Axiom MCP Server
by zed-extensions
A Zed extension for the Axiom MCP server. It allows Zed to interact with an Axiom MCP server.
Last updated: N/A
What is Axiom MCP Server?
This is a Zed extension that enables Zed to communicate with an Axiom MCP server. It provides a way to integrate Zed with Axiom's monitoring and control plane.
How to use Axiom MCP Server?
To use this server, first create a config.txt file containing your Axiom API token. Then, in your Zed settings.json, add the path to the config.txt file to the config_path setting under context_servers for mcp-server-axiom.
Key features of Axiom MCP Server
Integration with Axiom MCP
Configuration via config file
Easy setup within Zed
Enables Zed to leverage Axiom's capabilities
Use cases of Axiom MCP Server
Monitoring Zed instances using Axiom
Controlling Zed instances using Axiom
Integrating Zed with Axiom's ecosystem
Centralized management of Zed instances
FAQ from Axiom MCP Server
What is an Axiom API token?
What is an Axiom API token?
An Axiom API token is a credential that allows you to authenticate with the Axiom service.
Where do I get an Axiom API token?
Where do I get an Axiom API token?
You can obtain an Axiom API token from your Axiom account settings.
What is the purpose of the config.txt file?
What is the purpose of the config.txt file?
The config.txt file stores the configuration settings for the Axiom MCP server, such as the API token.
Can I store the API token directly in settings.json?
Can I store the API token directly in settings.json?
While technically possible, it is generally recommended to store sensitive information like API tokens in a separate file for security reasons.
What happens if I don't configure the config_path correctly?
What happens if I don't configure the config_path correctly?
Zed will not be able to connect to the Axiom MCP server, and the extension will not function properly.