N33RD MCP Server
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., "@N33RD MCP Server Show me usage analytics for consumer abc-123"
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.
N33RD MCP Server
Model Context Protocol server for the N33RD platform. Enables AI agents to programmatically manage API services, consumers, and keys.
What is This?
This MCP server exposes N33RD platform operations to AI assistants like Claude, allowing them to:
As Partner: Manage upstream services, create/manage consumers, configure authentication, handle API keys
As Consumer: View usage analytics, rotate own API key, check plan limits
NOT Supported (Manual-Only for Security):
Stripe Operations: All Stripe credential and billing operations must be manual
📚 Complete Documentation: See MCP_SERVER.md for comprehensive guide including security, permissions, Stripe operations, audit/compliance, and troubleshooting.
Related MCP server: SMB AI Command Platform MCP Server
Installation
npm install -g @tonkabits/n33rd-mcp-serverOr use directly with npx:
npx @tonkabits/n33rd-mcp-serverConfiguration
Claude Desktop
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"n33rd-partner": {
"command": "npx",
"args": ["-y", "@tonkabits/n33rd-mcp-server"],
"env": {
"N33RD_API_KEY": "your_partner_api_key_here",
"N33RD_ROLE": "partner"
}
}
}
}Claude Code (CLI)
Add to your project's .claude/settings.json:
{
"mcpServers": {
"n33rd": {
"command": "npx",
"args": ["-y", "@tonkabits/n33rd-mcp-server"],
"env": {
"N33RD_API_KEY": "your_api_key_here",
"N33RD_ROLE": "partner"
}
}
}
}Environment Variables
N33RD_API_KEY(required) - Your N33RD API keyN33RD_ROLE(required) - Role:partnerorconsumerN33RD_URL(optional) - API base URL (default:https://api.n33rd.com)
Available Tools
Partner Role
Service Management:
list_services- List all configured servicescreate_service- Add new upstream serviceupdate_service- Update service configurationconfigure_service_auth- Configure authentication (Bearer, Basic, API Key, OAuth2)
Consumer Management:
list_consumers- List all consumerscreate_consumer- Create consumer with API keyget_consumer- Get consumer details and usagerotate_consumer_key- Rotate consumer's API keyrevoke_consumer_key- Permanently revoke keyreactivate_consumer_key- Reactivate revoked keytoggle_consumer_key- Temporarily enable/disable key
Plan Management:
list_plans- List pricing planscreate_plan- Create new plan
Analytics:
get_dashboard- Partner dashboard with analytics
Consumer Role
get_dashboard- Consumer dashboard with usageget_analytics- Detailed usage analyticsrotate_my_key- Rotate own API keyget_plan_info- Current plan information
Usage Examples
With Claude Desktop
Once configured, you can ask Claude:
"List all my API services"
"Create a new consumer with email john@example.com on the trial plan"
"Show me the usage for consumer ID abc-123"
"Rotate the API key for consumer xyz-789"
"Configure Bearer token authentication for service srv_abc with token sk_live_..."
With Claude Code
cd /path/to/your/project
claudeThen in the CLI:
"List all my consumers and their usage"
"Create a new service called 'Books API' with base URL https://api.books.com"
"Show me which consumers are close to their rate limits"
Use Cases
AI Agent as Consumer
An AI agent can register itself as a consumer and access your API:
Partner creates landing page with auto-approval
AI agent calls
create_consumer(or signs up via landing page)Agent receives API key automatically
Agent makes requests through N33RD proxy
All requests are metered and billed
Example:
User: "I need to access the Books API"
AI: [Uses create_consumer tool]
AI: "I've registered for access. Here's my API key: books_api_live_abc123..."
AI: [Makes requests through https://api.n33rd.com/p/yourname/books/search?q=science]AI Agent as Partner
An AI agent can manage an entire API service:
Partner gives AI agent their API key
AI configures upstream services
AI creates/manages consumer keys
AI monitors usage and rotates keys
AI responds to usage alerts
Example:
User: "Create 5 test API keys for our QA team"
AI: [Uses create_consumer tool 5 times]
AI: "Created 5 keys. Here are the credentials..."
User: "Rotate all keys that haven't been used in 30 days"
AI: [Checks usage via get_consumer, rotates stale keys]
AI: "Rotated 3 inactive keys and sent emails with new credentials"Security
API keys are not stored - Only passed via environment variables
Encrypted in transit - All requests use HTTPS
Role-based access - Tools filtered by role (partner/consumer)
Same authentication as platform - Uses existing N33RD auth
Development
# Clone repository
git clone https://github.com/tonkabits/n33rd-mcp-server.git
cd n33rd-mcp-server
# Install dependencies
npm install
# Build
npm run build
# Run in development mode
export N33RD_API_KEY=your_key
export N33RD_ROLE=partner
npm run devTesting
Test the MCP server with the MCP Inspector:
npm install -g @modelcontextprotocol/inspector
mcp-inspector npx @tonkabits/n33rd-mcp-serverContributing
Contributions welcome! Please open an issue or PR on GitHub.
License
MIT
Links
N33RD Platform: https://n33rd.com
API Documentation: https://api.n33rd.com/docs
Model Context Protocol: https://modelcontextprotocol.io
Available Tools
14 toolsconfigure_service_authC
Configure authentication for a service
Inputs: auth_type (required), service_id (required), auth_config (required).
create_consumerB
Create a new consumer with API key
Inputs: tier (required), email (required).
create_planB
Create a new pricing plan
Inputs: tier (required), rate_limit_per_day (required), stripe_price_id, requests_included.
create_serviceA
Add a new upstream service to proxy requests through
Inputs: name (required), base_url (required), description.
get_consumerC
Get consumer details and usage
Inputs: consumer_id (required).
get_dashboardB
Get partner dashboard with analytics
Inputs: no named parameters.
list_consumersA
List all consumers for this partner
Inputs: no named parameters.
list_plansA
List all pricing plans for this partner
Inputs: no named parameters.
list_servicesA
List all services configured by this partner
Inputs: no named parameters.
reactivate_consumer_keyA
Reactivate a previously revoked consumer key
Inputs: consumer_id (required).
revoke_consumer_keyB
Permanently revoke a consumer API key
Inputs: consumer_id (required).
rotate_consumer_keyC
Rotate a consumer API key
Inputs: consumer_id (required).
toggle_consumer_keyB
Temporarily enable/disable a consumer API key
Inputs: enabled (required), consumer_id (required).
update_serviceC
Update an existing service configuration
Inputs: service_id (required), name, base_url, description.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 14 tools
Most tools clearly target distinct resources and actions, but the key lifecycle tools (revoke, reactivate, toggle, rotate) are closely related and could be confused despite helpful descriptions. Still, each has a defined role.
All tool names follow a consistent verb_noun snake_case pattern, such as list_consumers, create_service, rotate_consumer_key, and list_plans. No mixed naming conventions or vague generic verbs appear.
With 14 tools, the set is well-scoped for a partner/API management server. Each major area—consumers, services, plans, and dashboard analytics—has appropriate coverage without excessive redundancy.
The consumer key lifecycle is well covered, but there are notable CRUD gaps: no delete_service, no update_consumer, no delete_plan, and no update_plan. Create/list/update exists for services, but other core resources lack full lifecycle coverage.
Maintenance
Related MCP Connectors
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
AI service marketplace — agents discover, call, and pay for API services automatically.
Give your AI hands. Identity, credential vault, and API gateway for autonomous agents.
Connect AI agents to 580+ APIs with OAuth or API-key auth. Hosted gateway; API pricing varies.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables complete AI agent lifecycle management through MoluAbi's platform, allowing users to create, manage, and interact with AI assistants. Provides comprehensive tools for agent operations with secure authentication, usage tracking, and payment integration.9,324 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with SMB platform APIs for querying business data, managing tasks, accessing connectors, dashboards, and monitoring security.16MIT

Axonity Flow MCP Serverofficial
AlicenseAqualityAmaintenanceEnables AI agents to author and manage workflows, agents, tools, skills, policies, and reference docs in an Axonity tenant via the public REST API, with guardrails preventing direct publishing and secret exposure.100541 npmMIT- FlicenseAqualityCmaintenanceEnables role-based interaction with iGrid-Prometheus APIs, including domain listing, AI agent execution, action proposal, and CSV ingest/export, supporting Read, Write, and Admin permission levels.8-