What does an MCP interface for Lightning look like?
@hanna-paasivirta is already working on this.
Since Aug 14, 2025.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
This is an issue to explore what an MCP interface to Lightning might look like
If we were to expose an API to AI services to speak to Lightning, what would it cost? What functionality might expose? What do we need to actually do? What would a reference implementation look like?
I'd prefer to see a focus on read-only APIs here ("get me a list of workflows that failed last week"), but there may be value in write access ("create me a new workflow which does this") or execution stuff ("run this workflow for me")
The initial idea isn't so much to implement an MCP interface, just to get first draft of a spec together so that we can plan to build something out.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.