Last updated on November 1, 2026
Available tools
Every tool the Appnigma MCP server offers your coding agent, with an example and its parameters.
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. Pass both to file one build per platform with the same requirements.
check_statusList your engagements, or get one's steps, open questions and an ETA while work is running
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.
request_releaseAsk Appnigma to release a version that's already built
Try“Ask Appnigma to release version 0.8.0.1.”
For a version that should go out as it is. To change the code first, use request_change. On Salesforce this promotes a built beta version to Released, so your customers can install it in production. A release is permanent, so Appnigma's team performs it. To see whether it has gone out, ask again later naming the same version: left out, the newest unreleased version is picked, which may be a newer one. For a HubSpot app, a person on our team handles the request and confirms with you directly.
Which integration to release. Only needed if you have more than one.
The version to release, like 0.8.0.1. Leave it out to release the newest built version that isn't released yet.
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 |