Skip to main content

MCP Tools Reference

The Appgrammar MCP server exposes 31 tools via the Model Context Protocol. These tools allow AI coding agents to create, execute, transform, compose, and analyze appgrammars programmatically.

Connection

Add the following to your MCP client configuration (e.g. claude_desktop_config.json):

{
"mcpServers": {
"appgrammar": {
"url": "https://api.appgrammar.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_MCP_TOKEN>"
}
}
}
}

Generate your MCP token from the MCP Setup page.

Tools by Axiom

Axiom I — Compression

"Knowledge compresses. Execution expands."

ToolDescriptionMulti-turn
appgrammar_createCreate a new appgrammar blueprint from a natural-language description.Yes
appgrammar_create_submitSubmit LLM output for the current step in the appgrammar creation pipeline.Yes
appgrammar_decompileReverse-engineer an existing codebase into an executable appgrammar.Yes
appgrammar_decompile_submitSubmit LLM output for the current step in the decompilation pipeline.Yes
appgrammar_holographic_docGenerate a holographic documentation artifact from an appgrammar.Yes

Axiom II — Context

"Agent quality degrades monotonically with context size."

ToolDescriptionMulti-turn
appgrammar_startStart executing an appgrammar blueprint and receive the first step.No
appgrammar_nextGet the next step in an appgrammar blueprint execution.No
appgrammar_statusGet the status of an appgrammar execution including steps completed and total steps.No
appgrammar_swarm_partitionPartition an appgrammar into parallel execution swarms.Yes
appgrammar_semantic_rollbackCreate a semantic rollback point for an appgrammar.Yes

Axiom III — Governance

"Ungoverned agents are liabilities."

ToolDescriptionMulti-turn
appgrammar_inoculationInoculate an appgrammar against common failure patterns.Yes
appgrammar_phenotypingAnalyze the phenotype of an appgrammar — its observable characteristics, behaviors, and output patterns.Yes

Axiom IV — Architecture

"Application structure is composable, forkable, and heritable."

ToolDescriptionMulti-turn
appgrammar_breedBreed two appgrammars by analyzing module graphs and merging selected modules from each parent.Yes
appgrammar_forkFork a public appgrammar to create your own independent copy.No
appgrammar_spliceSplice two appgrammars together at compatible module boundaries.Yes
appgrammar_shatterShatter an appgrammar into its atomic module components.Yes
appgrammar_weaveWeave multiple appgrammar modules into a unified blueprint.Yes

Axiom V — Ecosystem

"When intent is legible, the ecosystem becomes navigable."

ToolDescriptionMulti-turn
appgrammar_searchSearch the appgrammar registry for public blueprints.No
appgrammar_broadcastSend a broadcast notification to all subscribers, forkers, and team members of an appgrammar.No
appgrammar_topological_searchSearch the appgrammar registry using topological similarity.Yes
appgrammar_upstream_shieldApply an upstream shield to an appgrammar to protect against breaking dependency changes.Yes

Axiom VI — Transformation

"Intent is invariant under transformation."

ToolDescriptionMulti-turn
appgrammar_transmuteTransmute an appgrammar from one technology stack to another while preserving architectural intent.Yes
appgrammar_distillDistill an appgrammar to its essential components.Yes
appgrammar_amplifyAmplify an appgrammar by expanding its modules with additional detail, tests, and documentation steps.Yes
appgrammar_style_transferTransfer the coding style and conventions from one appgrammar onto another while preserving functionality.Yes

Axiom VII — Algebra

"Structure admits a closed algebra."

ToolDescriptionMulti-turn
appgrammar_subtractSubtract one appgrammar from another, removing modules and steps present in the second from the first.Yes
appgrammar_intersectCompute the intersection of multiple appgrammars, returning only shared modules and steps.Yes
appgrammar_differenceCompute the symmetric difference between two appgrammars, highlighting unique modules in each.Yes
appgrammar_fuzzFuzz an appgrammar by introducing controlled variations to test robustness and discover edge cases.Yes
appgrammar_updateUpdate an existing appgrammar to reflect codebase changes.Yes

Shared

Infrastructure shared across multi-turn tool operations.

ToolDescriptionMulti-turn
appgrammar_tool_submitSubmit data for a multi-turn tool operation.Yes

Multi-turn Protocol

Many tools use a multi-turn protocol where the initial call returns a prompt and token rather than a final result. The workflow is:

  1. Call the tool — receive a prompt, expected output schema, and a single-use token
  2. Run the prompt on your LLM with the provided schema constraints
  3. Submit the result via appgrammar_tool_submit with the token and structured output
  4. Repeat until the operation returns a final result instead of another prompt

Tokens are single-use UUIDs that expire after 30 minutes. If a submission fails validation, a retry_token is provided with remaining retries.