axm-mcp
MCP transport and runtime discovery for installed AXM tools.
Start with the Quick Start to connect a client, inspect the catalog and call a read-only code-analysis tool.
What is included?
The server discovers axm.tools entry points from its own Python environment.
A compact facade (axm_search, axm_describe, axm_call,
axm_capabilities) keeps the direct MCP list small; the full catalog
remains reachable. Discovered tools may opt into direct exposure.
Built-ins are verify, web_fetch and list_tools. Their registration
does not mean their optional backends are installed. Choose the forge
extra for developer tools; all adds bibliography and tickets, but not
Scrapling. See built-in contracts.
Choose a guide
| You want to… | Read |
|---|---|
| Connect for the first time | Quick Start |
| Add an operation | Add a tool |
| Keep one process available | HTTP setup |
| Understand quality findings | Use verify |
| Look up flags and paths | CLI / configuration |
| Understand output or a missing tool | Facade contracts |
| Set per-session scopes | Shared write contracts |
| Understand implementation choices | Architecture |
| Embed or inspect the package | Python API |
Stdio is the default transport. HTTP does not itself require per-session authorization; shared policy is a separate configuration with documented limits. Always pass explicit absolute project paths to tools on a persistent server.