Skip to main content
Glama
N33RD MCP Server
by tonkabits

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-server

Or use directly with npx:

npx @tonkabits/n33rd-mcp-server

Configuration

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 key

  • N33RD_ROLE (required) - Role: partner or consumer

  • N33RD_URL (optional) - API base URL (default: https://api.n33rd.com)

Available Tools

Partner Role

Service Management:

  • list_services - List all configured services

  • create_service - Add new upstream service

  • update_service - Update service configuration

  • configure_service_auth - Configure authentication (Bearer, Basic, API Key, OAuth2)

Consumer Management:

  • list_consumers - List all consumers

  • create_consumer - Create consumer with API key

  • get_consumer - Get consumer details and usage

  • rotate_consumer_key - Rotate consumer's API key

  • revoke_consumer_key - Permanently revoke key

  • reactivate_consumer_key - Reactivate revoked key

  • toggle_consumer_key - Temporarily enable/disable key

Plan Management:

  • list_plans - List pricing plans

  • create_plan - Create new plan

Analytics:

  • get_dashboard - Partner dashboard with analytics

Consumer Role

  • get_dashboard - Consumer dashboard with usage

  • get_analytics - Detailed usage analytics

  • rotate_my_key - Rotate own API key

  • get_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
claude

Then 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:

  1. Partner creates landing page with auto-approval

  2. AI agent calls create_consumer (or signs up via landing page)

  3. Agent receives API key automatically

  4. Agent makes requests through N33RD proxy

  5. 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:

  1. Partner gives AI agent their API key

  2. AI configures upstream services

  3. AI creates/manages consumer keys

  4. AI monitors usage and rotates keys

  5. 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 dev

Testing

Test the MCP server with the MCP Inspector:

npm install -g @modelcontextprotocol/inspector
mcp-inspector npx @tonkabits/n33rd-mcp-server

Contributing

Contributions welcome! Please open an issue or PR on GitHub.

License

MIT

Available Tools

14 tools
configure_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

    B3.4/5.0

    Scored across 14 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables 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.
      100
      541 npm
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables 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
      -