AT
- other
2
GitHub Stars
other
Language
6 months ago
First Indexed
2 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": {
"zambrella-at_mcp_server": {
"command": "/Users/douglastodd/Projects/atsign/at_mcp_server/at_mcp_server.exe",
"args": []
}
}
}You can run an MCP server that exposes MCP-compliant endpoints for your client apps. This server acts as the bridge between your local environment and MCP clients, enabling you to manage and query MCP resources through a consistent interface. This guide shows how to use the atsSign MCP server, how to install and run it, and practical notes to keep in mind as you work with MCP tools and inspectors.
How to use
You run the MCP server locally to access MCP endpoints from your client. Start the server process and point your MCP client to the server according to the method you prefer (local stdio or a remote HTTP URL). When the server is running, you can perform actions like listing all available atkeys, filtering them by shared state, and retrieving the value of a specific atkey. Use the server as a routable backend for your MCP-enabled client applications, enabling scripted workflows and tooling that depend on MCP data.
How to install
Prerequisites you need before installing the MCP server:
- Dart SDK for building the executable
- A compatible shell or command prompt to run the binary
- Optional: Node.js if you plan to use the MCP Inspector tooling alongside the server Proceed with these concrete steps to prepare and run the server.
# Install Dart tools if not present
# (follow your OS-specific instructions for Dart installation)
# Build the MCP server executable (from source code)
dart compile exe bin/main.dart -o at_mcp_server.exe
# Run the server (adjust path to your built binary as needed)
./at_mcp_server.exe
Additional notes
Explore MCP inspector tooling for debugging and verification of your MCP setup. You can run the inspector with a local configuration to connect to your atsSign MCP server and inspect endpoints and data.
# Example usage for the MCP Inspector
npx @modelcontextprotocol/inspector --config mcp_inspector_config.json --server at-sign-tools
Available tools
get_all_atkeys
Retrieves all atkeys available on the MCP server and supports filtering by shared with, shared by, or a regex pattern.
filter_atkeys
Applies filters to the list of atkeys to narrow results based on sharing relationships or patterns.
get_atkey_value
Fetches the current value for a specific atkey from the MCP server.