DeSo MCP Server
OfficialThe DeSo MCP Server transforms Cursor IDE's AI assistant into a comprehensive DeSo development expert, offering tools for:
Explore DeSo APIs: Access detailed documentation and code examples for all DeSo API categories (social, financial, NFT, identity)
Generate Production Code: Create ready-to-use code snippets for DeSo operations in JavaScript, TypeScript, React, or cURL
Guide deso-js SDK Usage: Learn setup, authentication, transactions, and best practices
Understand DeSo Architecture: Get explanations of systems, transaction flows, and integration patterns
Search DeSo Repositories: Find documentation and resources across repositories
Debug Common Issues: Solve integration problems with real solutions
Implement Best Practices: Learn proven patterns for messaging flows, error handling, and state management
Access UI Components: Explore 40+ professional React components for building DeSo applications
Query Blockchain Data: Convert natural language to optimized GraphQL queries
Develop Complete Apps: Build scalable, production-ready DeSo applications with framework-specific examples
Generates curl commands for interacting with DeSo blockchain APIs, allowing for testing and debugging of DeSo operations directly from the command line.
Provides DeSo GraphQL schema and integration guidance for querying the DeSo blockchain through GraphQL.
Provides comprehensive code generation for DeSo blockchain operations using JavaScript, with detailed guidance on implementing DeSo features.
Provides Next.js-specific implementation patterns for DeSo blockchain integration, including server-side integration and API routes.
Supports Node.js implementation patterns for server-side DeSo blockchain integration with detailed SDK setup guidance.
Offers React component patterns and implementation guidance for DeSo blockchain integration, including authentication flows and state management.
Includes modern UI examples with Tailwind CSS for DeSo applications, demonstrated in the complete messaging application example.
Generates TypeScript code examples for DeSo blockchain integration with type safety, supporting professional-grade DeSo application development.
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., "@DeSo MCP Server how do I submit a post to the DeSo blockchain?"
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.
DeSo MCP Server v3.0 (HTTP)
A comprehensive Model Context Protocol (MCP) server for DeSo blockchain development, now with HTTP transport support.
Features
🛠️ 10 Comprehensive Tools:
deso_api_explorer- Complete DeSo API documentation and examplesdeso_js_guide- deso-js SDK setup and usage guidesgenerate_deso_code- Generate code examples for DeSo operationsexplain_deso_architecture- Architectural explanations and patternsrepository_search- Search DeSo repository documentationread_repository_document- Read specific DeSo docsdeso_debugging_guide- Real debugging fixes for common issuesdeso_implementation_patterns- Best practices from production appsdeso_ui_components- Complete UI component library guidedeso_graphql_helper- GraphQL query builder and examples
🚀 HTTP Transport:
RESTful HTTP API instead of stdio
CORS support for web integration
Health check endpoint
Easy deployment and scaling
Related MCP server: AMOCA Solana MCP Server
Quick Start
Local Development
# Install dependencies
npm install
# Start the server
npm start
# Development with auto-reload
npm run devThe server will run on http://localhost:3000 by default.
Environment Variables
PORT=3000 # Server port (default: 3000)
HOST=localhost # Server host (default: localhost)Docker Deployment
# Build the image
npm run docker:build
# Run the container
npm run docker:run
# Or manually:
docker build -t deso-mcp-server .
docker run -p 3000:3000 -e HOST=0.0.0.0 deso-mcp-serverHTTP Endpoints
Health Check
curl http://localhost:3000/MCP Tool Requests
Send JSON-RPC requests to the root endpoint.
Important:
MCP requires initialization first, then you can call tools
Always include the
Accept: application/json, text/event-streamheaderThe server runs in stateless mode (no session management required)
# 1. Initialize the MCP session
curl -X POST http://localhost:3000/ \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "initialize",
"params": {
"capabilities": {},
"protocolVersion": "2024-11-05",
"clientInfo": {"name": "my-client", "version": "1.0.0"}
}
}'
# 2. List available tools
curl -X POST http://localhost:3000/ \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 2,
"method": "tools/list"
}'
# 3. Call a specific tool
curl -X POST http://localhost:3000/ \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{
"jsonrpc": "2.0",
"id": 3,
"method": "tools/call",
"params": {
"name": "deso_api_explorer",
"arguments": {
"category": "social",
"includeCode": true
}
}
}'Example Usage
JavaScript Client Example
class DesoMCPClient {
constructor(baseUrl = 'http://localhost:3000') {
this.baseUrl = baseUrl;
this.initialized = false;
}
async request(method, params = {}) {
const response = await fetch(this.baseUrl, {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Accept': 'application/json, text/event-stream'
},
body: JSON.stringify({
jsonrpc: '2.0',
id: Date.now(),
method,
params
})
});
const data = await response.json();
if (data.error) throw new Error(data.error.message);
return data.result;
}
async initialize() {
await this.request('initialize', {
capabilities: {},
protocolVersion: '2024-11-05',
clientInfo: { name: 'deso-client', version: '1.0.0' }
});
this.initialized = true;
}
async callTool(name, args) {
if (!this.initialized) await this.initialize();
return this.request('tools/call', { name, arguments: args });
}
}
// Usage examples:
const client = new DesoMCPClient();
// Get DeSo API Information
const apiInfo = await client.callTool('deso_api_explorer', {
category: 'social',
endpoint: 'submit-post',
includeCode: true
});// Debug DeSo Integration Issues const debugInfo = await client.callTool('deso_debugging_guide', { issue: 'message-decryption', includeCode: true });
// Generate GraphQL Queries const query = await client.callTool('deso_graphql_helper', { action: 'build', question: 'How many followers does nader have?', username: 'nader' });
## Integration with MCP Clients
### Claude Desktop Configuration
Add to your Claude Desktop configuration:
```json
{
"mcpServers": {
"deso": {
"command": "npx",
"args": ["deso-mcp-server"],
"transport": "http",
"url": "http://localhost:3000"
}
}
}VS Code Integration
Use with MCP-compatible VS Code extensions by configuring the HTTP endpoint:
{
"mcp.servers": [
{
"name": "deso",
"transport": "http",
"url": "http://localhost:3000"
}
]
}Architecture
The server uses:
HTTP Transport: RESTful API with JSON-RPC over HTTP
CORS Support: Cross-origin requests enabled
Graceful Shutdown: Proper cleanup on SIGINT/SIGTERM
Error Handling: Comprehensive error responses
Health Checks: Built-in monitoring endpoint
Development
Project Structure
deso-mcp/
├── deso-mcp.js # Main MCP server
├── package.json # Dependencies and scripts
├── Dockerfile # Container configuration
└── README.md # DocumentationDebugging
Enable debug logging with
DEBUG=mcp:*Check server health at
http://localhost:3000/Monitor logs for request/response details
License
MIT License - see LICENSE file for details.
Contributing
Fork the repository
Create a feature branch
Make your changes
Test with HTTP requests
Submit a pull request
Support
For issues and questions:
GitHub Issues: deso-protocol/mcp-server
DeSo Documentation: docs.deso.org
Developer Discord: DeSo Developers
Available Tools
8 toolsdeso_api_explorerC
Comprehensive DeSo API explorer with backend implementation details and deso-js SDK integration
Inputs: category, endpoint, includeCode.
deso_debugging_guideC
Comprehensive debugging guide for common DeSo integration issues with solutions
Inputs: issue (required), includeCode.
deso_implementation_patternsC
Best practices and implementation patterns learned from deso-chat and real debugging
Inputs: pattern (required), framework.
deso_js_guideC
Complete guide to using the deso-js SDK with setup, authentication, and transactions
Inputs: topic (required), framework.
explain_deso_architectureC
Explain DeSo architecture, flows, and integration patterns
Inputs: topic (required), includeCode.
generate_deso_codeB
Generate comprehensive code examples for DeSo operations using deso-js SDK
Inputs: language (required), operation (required), fullExample, includeAuth.
read_repository_documentB
Read a specific document from the DeSo repository
Inputs: path (required), repository.
repository_searchC
Search for documents in the DeSo repository
Inputs: query (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
The tools have some overlap in purpose, particularly between deso_api_explorer, deso_js_guide, and generate_deso_code, which all involve code/API guidance, but their descriptions help differentiate them. However, tools like deso_debugging_guide and deso_implementation_patterns could be confused as they both address integration issues and best practices, creating ambiguity in selection.
Most tools follow a consistent snake_case pattern with a 'deso_' prefix, such as deso_api_explorer and deso_js_guide, which aids readability. However, there are minor deviations like read_repository_document and repository_search, which use a different naming style without the prefix, slightly breaking the pattern but not severely impacting usability.
With 8 tools, the count is well-scoped for a server focused on DeSo integration, documentation, and code generation. Each tool appears to serve a distinct educational or operational purpose, avoiding bloat while covering key aspects like API exploration, debugging, and repository access, making the set manageable and purposeful.
The tool set covers documentation, guidance, and repository operations well, but there are notable gaps in direct DeSo API interactions, such as creating or updating blockchain transactions or user data. While tools like generate_deso_code and deso_js_guide provide code examples, they lack actual execution capabilities, which limits the server's operational completeness for real-time integration tasks.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Marketo MCP server for AI. 130 tools to operate Marketo from Claude, Cursor, or ChatGPT.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants to explore and interact with Cursor IDE's SQLite databases, providing access to project data, chat history, and composer information.26-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI models to interact with the Solana blockchain, providing RPC methods, wallet management, DeFi trading capabilities, and Helius API integration for enhanced Solana development.5MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for creating, updating, and querying semantic relationships (cyberlinks) on Cosmos-based blockchains through integration with Cursor IDE and Claude Desktop.1-

CodeAlive MCPofficial
AlicenseNot gradedqualityBmaintenanceA Model Context Protocol server that enhances AI agents by providing deep semantic understanding of codebases, enabling more intelligent interactions through advanced code search and contextual awareness.91MIT