gravity-agent-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gravity-agent-mcp Query wallet 0x1234 for token balances"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
gravity-agent-mcp
A next-generation Omni-Agent system built on the Model Context Protocol (MCP). gravity-agent-mcp is an intelligent, secure, context-aware assistant that bridges local cultural nuance (Khmer / Cambodian) with automation and Web3 capabilities, exposed to clients like Claude Desktop over a stdio transport.
1. The 7 Core Pillars
# | Pillar | Status | Where it lives |
1 | Localization & Khmer Culture Agent | β Implemented |
|
2 | Hyper-Personalized Productivity | π§© Stub (see note) |
|
3 | Decentralized / Web3 Agent | β Implemented |
|
4 | Cross-Platform Automation Agent | π Playbook |
|
5 | Security & Privacy Guard | β Implemented |
|
6 | Intelligent Routing | β Implemented |
|
7 | Zero-Configuration | β One-line config |
|
Note: Pillars 2/4 are not yet shipped as live tools.
create_calendar_event(productivity) andkhmer_greetingwere scaffolding and were removed during the modular refactor; the Automation Agent is currently documented as an orchestration playbook rather than a meta-tool. Add them assrc/tools/*.tsmodules to complete the set.
Related MCP server: Tyra Advanced Memory MCP Server
2. Tech Stack
Language: TypeScript (strict) / Node.js β₯ 18
Framework:
@modelcontextprotocol/sdkTransport: JSON-RPC 2.0 over Stdio
Client: Claude Desktop (or any MCP-compatible client)
3. Project Structure
gravity-agent-mcp/
βββ src/
β βββ index.ts # Entry point: Server init + Stdio transport
β βββ router.ts # Pillar 6 β dispatch (switch-case) + tool registry
β βββ core/
β β βββ types.ts # Shared contract (ToolMeta, ToolResult, ToolHandlerβ¦)
β βββ middleware/
β β βββ security.ts # Pillar 5 β withSecurityGuard() interceptor
β βββ tools/
β βββ khmerCulture.ts # Pillar 1 β get_khmer_culture_context
β βββ web3.ts # Pillar 3 β web3_blockchain_query
βββ docs/
β βββ automation-playbook.md# Pillar 4 β orchestration guide
βββ build/ # Compiled output (generated by tsc)
βββ package.json
βββ tsconfig.jsonThe entry point (src/index.ts) does only three things: initialize the
Server, attach ListTools/CallTool handlers (delegating to src/router.ts),
and connect over Stdio. All tool logic, guarding, and routing live in src/.
4. Tools
Tool | Category | Sensitive? | Description |
| culture | No | Returns localized Cambodian context for a topic ( |
| web3 | Yes | Inspects a wallet address on Ethereum/Solana; returns simulated native + token balances. Address format is regex-validated. |
Sensitive tools pass through the Security & Privacy Guard, which logs the intercept and runs a (simulated) confirmation gate before executing.
5. Setup
Prerequisites
Node.js β₯ 18 and npm.
Install & build
npm install # install dependencies (SDK + TypeScript)
npm run build # compile src/ β build/ (tsc)Run (stdio)
npm start # node build/index.jsThe server reads JSON-RPC requests from stdin and writes responses to stdout. All diagnostics (server/security/routing logs) go to stderr so the JSON-RPC stream on stdout stays clean β this is required for stdio MCP.
6. Connect to Claude Desktop (Zero-Config, Pillar 7)
Edit your claude_desktop_config.json (macOS:
~/Library/Application Support/Claude/claude_desktop_config.json;
Windows: %APPDATA%\Claude\claude_desktop_config.json). Add a mcpServers
entry pointing at the compiled build/index.js with an absolute path:
{
"mcpServers": {
"gravity-agent-mcp": {
"command": "node",
"args": [
"/absolute/path/to/gravity-agent-mcp/build/index.js"
]
}
}
}Common pitfalls (these cause the "pipe broke" error / no tool icon):
Pointing
argsatindex.tsinstead of the compiledbuild/index.js(Node can't run TypeScript directly).Using a relative path β Claude Desktop launches from a different cwd, so always use an absolute path.
Any
console.log/process.stdout.writein tool code corrupts the JSON-RPC stream. This project logs only viaconsole.error.Forgetting to run
npm installbeforenpm run build(missing SDK).
Restart Claude Desktop after editing the config; the tools/plug icon appears once the server handshakes successfully.
7. Example: call a tool over JSON-RPC
Send newline-delimited JSON-RPC messages on stdin:
{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"cli","version":"1.0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_khmer_culture_context","arguments":{"topic":"khmer_etiquette"}}}Expected tools/call result (truncated):
{
"content": [
{ "type": "text", "text": "{ \"topic\": \"khmer_etiquette\", \"title\": \"β¦\", \"dos\": [β¦], \"donts\": [β¦] }" }
]
}For web3_blockchain_query, the server logs a [SECURITY] Intercepted β¦ (sensitive: true)
line to stderr and runs the simulated confirmation before returning balances.
8. Development notes
Add a tool: create
src/tools/<name>.tsexportingdefinition: ToolMetaandexecute(args), then add acaseto theswitchinsrc/router.ts(wrap the call inwithSecurityGuard). Export itsdefinitionfromtoolDefinitionsforListTools.Security policy: mark a tool sensitive by setting
category: "web3"or"productivity"inSENSITIVE_CATEGORIES(src/core/types.ts). SetSECURITY_MODE.interactiveConfirmation = trueinsrc/middleware/security.tsto require a real client "Allow" prompt instead of the simulation.Build output:
build/is generated; it is safe to delete and regenerate withnpm run build.
Available Tools
2 toolsget_khmer_culture_contextA
Returns localized Cambodian context for a topic. Topics: legal_business_registration, khmer_etiquette, phnom_penh_zones.
Inputs: topic (required).
web3_blockchain_queryA
Inspects an on-chain wallet address on a given network (Ethereum, Solana). Returns simulated native + token balances.
Inputs: network (required), walletAddress (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 2 tools
The two tools are completely unrelated: one provides Cambodian cultural context, the other queries blockchain wallets. There is no overlap in purpose or functionality, so an agent can easily distinguish them.
Both tools use descriptive names with underscores, but one starts with 'get_' and the other with 'web3_', introducing a slight inconsistency in naming style. However, both are clear and predictable.
With only 2 tools covering disparate domains (culture and blockchain), the server feels underdeveloped. Either the server should focus on one domain with more tools, or additional related tools should be added to justify the mix.
Each individual tool appears adequate for its narrow purpose, but the server lacks a coherent domain, making it impossible to assess full lifecycle coverage. There are no obvious gaps within each tool, but the set as a whole is not comprehensive.
Related MCP Connectors
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
An MCP memory server. One memory your agents share β across models, devices and apps.
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
The OpenMesh MCP Server provides decentralized, permissionless cloud infrastructure that integrates AI assistants with Web2 and Web3 applications without middlemen. It offers intelligent service discovery to identify MCP servers, acts as a universal proxy for routing requests to discovered services, implements performance optimization through usage feedback, and provides automatic fault tolerance with alternative services when servers become unavailable.
Related MCP Servers
AlicenseCqualityDmaintenanceAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.37178GPL 3.0- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
- AlicenseAqualityDmaintenanceAn MCP server that powers AI agents with indexed blockchain data from The Graph.3MIT
- AlicenseAqualityDmaintenanceA local-first MCP server that enables AI agents to query the Sui blockchain using gRPC, GraphQL, and Archival Service, with auto-routing and LLM-friendly responses.295Apache 2.0