Last updated on September 24, 2026
Connect Your Coding Agent
Give Claude Code, Cursor or Codex live access to your Appnigma account — file integration work, check progress and answer questions without leaving your editor.
Connect
Pick your agent. Setup is one command plus a one-time sign-in in your browser — no API key, and nothing secret is written to your project.
Run this in your project folder:
claude mcp add --transport http appnigma https://engine.appnigma.ai/mcp && claude mcp login appnigmaYour browser opens. Sign in to Appnigma and click Allow.
Create .cursor/mcp.json in your project folder:
{
"mcpServers": {
"appnigma": { "url": "https://engine.appnigma.ai/mcp" }
}
}Then open Customize → MCPs, switch appnigma on, and click Authenticate. Your browser opens — sign in and click Allow.
Run:
codex mcp add appnigma --url https://engine.appnigma.ai/mcpCodex starts the sign-in for you. Open the link it prints, sign in and click Allow.
Any MCP client that supports remote servers works. Add a server with:
- URL:
https://engine.appnigma.ai/mcp - Transport: Streamable HTTP
- Auth: OAuth — your client opens the Appnigma sign-in in your browser
On the permission page, check that the company and email shown are yours before you click Allow. You only sign in once — the connection stays active across sessions.
Check it works
Start a new chat with your agent and ask:
Check my Appnigma account.You're connected when the reply names your company. If your agent asks to run an Appnigma tool, approve it.
Optional: add this to your README.md or AGENTS.md so your agent knows when to reach for Appnigma:
Appnigma builds and maintains our integrations. It is connected as an MCP
server — use it to file integration work, check progress and answer its questions.Troubleshooting
| Problem | Fix |
|---|---|
| Agent can't find Appnigma | Restart your agent. In Cursor, check appnigma is switched on in Customize → MCPs. |
| Needs authentication | Sign in again: claude mcp login appnigma, codex mcp login appnigma, or Authenticate in Cursor. |
| Browser didn't open | Copy the sign-in link your agent shows and paste it into your browser. |
| "This request has expired" | Sign-in links last about ten minutes. Start the sign-in again. |
| Reply names the wrong company | You approved while signed in to another account. Sign out of Appnigma in your browser, then sign in again. |
| "No Appnigma account to connect" | Email support@appnigma.ai with the address you signed in with. |
Still stuck? Email support@appnigma.ai with your agent's name and the reply it gave.
Available tools
You don't call these yourself — ask your agent in plain words and it picks the tool and fills in the details. Open a tool to see an example and its parameters.
request_integrationFile a new integration request and get an engagement ticket
Try“Ask Appnigma to build a HubSpot integration that syncs our deals.”
What you want built, in plain language: the systems, the data or actions, and any constraints. Recorded word for word as the requirement.
Only needed when the request doesn't say which platform.
check_statusList your engagements, or get one's steps, ETA and open questions
Try“What's the status of our Appnigma work?”
Engagement reference, like eng_a1b2c3. Leave it out to list every engagement on your account.
answer_questionAnswer open questions so paused work can continue
Try“Answer Appnigma's open questions on eng_a1b2c3.”
The engagement the questions belong to.
Up to 20 question and answer pairs, each question in its exact wording from check_status. Send everything you can in one call.
get_tech_planRead the technical plan Appnigma drafted for an engagement
Try“Show me the tech plan for eng_a1b2c3.”
The engagement whose plan to fetch.
review_planApprove a plan to start the build, or send it back with changes
Try“Approve the plan for eng_a1b2c3.”
The engagement whose plan you're reviewing.
approve starts the build. request_changes sends the plan back for a revision.
The plan version from get_tech_plan. If the plan changed since you read it, the decision is refused.
What should be different. Required when the decision is request_changes.
request_changeRequest a change to an integration that has already shipped
Try“Ask Appnigma to also sync the deal owner field.”
What should be different about the live integration. Recorded word for word as the requirement.
Which integration to change. Only needed if you have more than one.
get_accountConfirm the connection and see your company, platforms and integrations
Try“Check my Appnigma account.”
No parameters.
Technical details
| Setting | Value |
|---|---|
| Server URL | https://engine.appnigma.ai/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth sign-in in your browser, as the same account you use in the Appnigma web app |
| Session | Stays signed in; re-authenticate after about a month without use |