What is MCP used for here?
Model Context Protocol gives compatible assistants a standard way to call tools. Lanelet exposes tools for a small set of board operations. The assistant can inspect active work and make the ticket changes you ask for.
For example, you might ask an assistant to create a ticket from a meeting note or update the description after a discussion. It still needs the correct board and your intended change. Clear instructions help prevent ambiguous edits.
How do I connect an assistant?
Open Settings → MCP in your team. Give the token a recognizable name, create it, and copy it immediately. Lanelet only shows the token once. Configure your MCP client with the /api/mcp endpoint on your app’s domain and an Authorization: Bearer header containing the token.
The endpoint uses stateless Streamable HTTP. Your client must support a custom bearer token; this implementation does not provide automatic OAuth discovery. Check the connection guide for an example configuration.
Which tools can the assistant call?
The available tools are list_boards, list_tickets, create_ticket, edit_ticket, delete_ticket, and restore_ticket. They operate in the team selected when the token was created. They cannot invite people, change account security, or permanently delete tickets early.
For edits, include the current ticket version when possible. That makes a stale edit fail rather than silently overwriting a teammate’s newer change. Deleting moves the card to the bin, where it remains recoverable for 30 days.
How can I remove access?
Revoke the token in Settings → MCP. The next request with that token will be rejected. Removing a person from a team also revokes their team tokens. Tokens expire after 90 days, so create a replacement when needed.
A token is a credential. Keep it in your MCP client’s secret storage and avoid placing it in a ticket, a public repository, or a blog post. A named token for each assistant makes access easier to review.