Leiga for AI agents
Leiga is an AI-assisted project management tool that helps teams plan work, track issues, and automate routine project tasks like status updates and reporting. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Leiga.
Look up an issue's detail
Pull the full detail of an issue by its number to answer a status question.
Check a project's overview
Read a project's overview and version list before a planning meeting, without changing any of its settings.
Create a new project
Set up a new project from a template when a team starts a fresh initiative.
10 Leiga actions, graded by risk.
Every Leiga action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
9Look things up. Allowed by default.
- leiga.get_file_listGet File List
- leiga.list_projectsList Projects
- leiga.get_issue_schemaGet Issue Schema
- leiga.get_version_listGet Version List
- leiga.get_webhook_type_listGet Webhook Type List
- leiga.get_project_informationGet Project Information
- leiga.get_project_template_listGet Project Template List
- leiga.get_project_overview_templateGet Project Overview Template
- leiga.get_issue_detail_by_issue_numberGet Issue Detail by Number
write
1Create and change things. Allow, or ask the user first.
- leiga.create_projectCreate Project
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Leiga in three steps.
- 01Your users connect LeigaThey add their Leiga api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “create Project” can wait for the user to approve.
- 03Any agent can actYour agent calls Leiga through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('leiga', { read: 'allow', write: 'ask', // create_project destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Leiga connects.
Users add their Leiga api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Leiga connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Leiga from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraphMore project management apps.
Leiga and Arc0, answered.
Can I use Leiga with Claude, ChatGPT or Cursor?
Yes. Connect Leiga to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Leiga actions you allow.
How do users connect Leiga?
Users add their Leiga api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Leiga actions can my agent take?
10 in total: 9 read, 1 write and 0 destructive, such as “create Project”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Leiga?
Yes. Allow read actions and deny writes in the Leiga policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Leiga too?
Yes. The same Leiga connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Leiga into your agent.
Your users connect Leiga once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan