axone-mcp

Created By
axone-protocola year ago
🤖 Axone’s MCP server – gateway to the dataverse for AI-powered tools
Overview

what is Axone MCP?

Axone MCP is a lightweight server that acts as a gateway to the dataverse, enabling AI-powered tools to interact with various resources through the Model-Context Protocol.

how to use Axone MCP?

To use Axone MCP, ensure you have Golang and Docker installed, then build the server using the command make build.

key features of Axone MCP?

  • Standardized access to Axone's capabilities via the Model-Context Protocol.
  • Authorization layer for secure access requests based on decentralized governance rules.
  • Integration with various clients and tools for seamless operation.

use cases of Axone MCP?

  1. Facilitating AI tool interactions with decentralized resources.
  2. Enabling secure data access for applications using the Model-Context Protocol.
  3. Supporting developers in building AI-powered applications with standardized protocols.

FAQ from Axone MCP?

  • What is the Model-Context Protocol?

It is a standardized protocol that allows for structured interactions between AI tools and resources.

  • Is Axone MCP open-source?

Yes! Axone MCP is open-source and available on GitHub.

  • What technologies are required to run Axone MCP?

You need Golang and Docker to build and run the server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
axone-protocol
Star
2
Language
Go
License
BSD-3-Clause license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago