Axiom Context Server

Provides a Model Context Server for Axiom to supply context to the Zed AI assistant during conversations.

other

0

GitHub Stars

other

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "axiomhq-zed-axiom-context-server": {
      "command": "/path/to/axiom-mcp",
      "args": [
        "--config",
        "/path/to/your/config.txt"
      ]
    }
  }
}

The Axiom Context Server extension provides a Model Context Server for Axiom to supply contextual information to the Zed AI assistant, enabling richer interactions and more accurate responses by leveraging Axiom’s context data.

How to use

Run the Axiom Context Server as an MCP within your Zed environment by configuring the extension to launch the axiom-mcp process with your chosen configuration. The server communicates via a local stdio channel and will expose the MCP endpoint that your client can connect to for retrieving or updating model context. You can customize the command and its arguments in your Zed settings so the extension starts the MCP with your preferred config file. If you do not specify a custom command, the extension will attempt to use an axiom-mcp executable found in the current directory.

How to install

Prerequisites: ensure the Axiom Context Server extension is installed in your Zed environment. No additional runtime environments are required beyond what the extension expects for executing the MCP binary.

Step-by-step setup:

How to install

{
  "context_servers": {
    "axiom-mcp": {
      "settings": {},
      "command": {
        "cmd": "/path/to/axiom-mcp",
        "args": ["--config", "/path/to/your/config.txt"]
      }
    }
  }
}

If no custom command is specified, the extension will look for an axiom-mcp executable in the current directory. Follow these steps to enable the server with a custom path or to rely on the default in your environment.

Additional sections

Configuration notes: In your Zed settings.json, you can define a dedicated context server named axiom-mcp with its own command and arguments. The example below demonstrates the exact structure you should use for a successful configuration.

{
  "context_servers": {
    "axiom-mcp": {
      "settings": {},
      "command": {
        "cmd": "/path/to/axiom-mcp",
        "args": ["--config", "/path/to/your/config.txt"]
      }
    }
  }
}

Notes on security and troubleshooting

Ensure the axiom-mcp executable has appropriate permissions and is accessible from the environment where the Zed extension runs.
If the extension cannot locate the executable, verify that the path in the settings.json is correct or place axiom-mcp in the current working directory of the Zed process.
The --config argument should point to a valid configuration file that the MCP can read. Keep the config file secure and avoid embedding sensitive credentials directly if not required.