MCP / AI / Announcement
Introducing the Leera MCP server: connect your AI client
Connect a compatible AI client to Leera with scoped access to supported project, issue, sprint, document, and QA tools. Start with a verified read and a clear task.
At a glance
Leera includes an MCP server for connecting compatible AI applications to supported workspace operations. The endpoint, authentication, available tools, and granted access determine what a connection can do. Check a familiar record before depending on a broader workflow.
A useful AI workflow needs the project context behind the task. Leera’s built-in Model Context Protocol server gives compatible AI clients access to supported workspace operations, so an assistant can retrieve current records and perform authorized actions without relying only on a pasted summary.
Bring project context into the tools you use
A coding assistant can read an issue’s acceptance criteria before implementation. A connected assistant can review a selected sprint or create an explicitly requested follow-up task. Supported QA tools can help record results produced by a tester or an automation system.
These are example workflows, and they require the relevant client support, tool access, and configuration. MCP does not execute a test just because a tool can save its result, and a successful tool call does not establish that an assistant’s interpretation is correct.
Choose access for the assignment
Leera supports appropriate OAuth connections and manually created scoped tokens. The method you use depends on the client and deployment. Review the requested access during consent, or select scopes and project restrictions when creating a token. Set an appropriate expiry and revoke credentials that no longer have a purpose.
A token’s plaintext secret is shown when it is created. Store it in the client’s supported credential mechanism and give the connection a meaningful name. A read-only sprint summary should not need the same access as an integration responsible for creating project records.
Check the available tool catalog
The supported surface includes project information and operations around issues, sprints, documents, and QA. What a specific connection sees depends on the exposed tools, enabled modules, and credential access. Do not assume every web control has an equivalent tool or that every client presents the same catalog.
Read the tool’s requirements and verify important results in Leera. For an action that creates a record, ask the client to return its identifier and read the saved record back. That makes the outcome easier to inspect.
Start with your actual endpoint
Copy the endpoint from your Leera settings and follow your client’s current connection instructions. A sample configuration for one client is not a universal format. For a self-hosted instance, make sure the public reverse proxy forwards /mcp to the backend alongside /api.
Test a familiar issue first, then perform one deliberate change in an appropriate trial project. Check the workspace, project, and saved result before expanding the workflow. The complete MCP guide includes example prompts, an access checklist, and troubleshooting steps.