Solenoid Now Works with Claude and Cursor via MCP

AI assistants are increasingly where developers live. Claude helps you think through architecture. Cursor writes your code. Why should managing infrastructure require switching to a dashboard?

Today we’re releasing @solenoid.systems/mcp — a Model Context Protocol server that connects Claude, Cursor, and other MCP-compatible assistants to all Solenoid APIs.

Zero-Install Setup

npx @solenoid.systems/mcp

That’s it. First run opens a browser for OAuth. Tokens are stored securely in your OS keychain. No API keys to manage, no config files to write.

What Your AI Can Now Do

Once connected, your assistant can interact with all six Solenoid products:

Meter — Check balances, deduct credits, refill accounts

"Check the credit balance for tenant acme_corp"
"Deduct 500 credits from user_123"

Gate — Manage feature flags

"List all feature flags"
"Enable the dark_mode flag"
"What's the current state of new_checkout?"

Relay — Schedule webhooks

"Schedule a webhook to https://api.partner.com/notify in 30 minutes"

Witness — Create tamper-proof receipts

"Notarize this document hash: abc123..."
"What's the status of my witness chain?"

Latch — Distributed locks

"Acquire a lock on resource deploy_production"
"Check if the migration_lock is held"

Pulse — Uptime monitoring

"Show me any failing monitors"
"Create a monitor for api.myapp.com/health"

Claude Desktop Configuration

Add to your Claude Desktop config:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "solenoid": {
      "command": "npx",
      "args": ["@solenoid.systems/mcp"]
    }
  }
}

Restart Claude. You’ll see Solenoid tools available in the tools panel.

Cursor Configuration

Add to .cursor/mcp.json in your project:

{
  "servers": {
    "solenoid": {
      "command": "npx",
      "args": ["@solenoid.systems/mcp"]
    }
  }
}

Now Cursor can manage your infrastructure while you code.

Scoping to Specific Products

Don’t need all six products? Enable only what you use:

{
  "mcpServers": {
    "solenoid": {
      "command": "npx",
      "args": ["@solenoid.systems/mcp", "--tools", "meter,gate,pulse"]
    }
  }
}

Why MCP?

Model Context Protocol is an open standard for connecting AI assistants to external tools. Instead of building separate integrations for Claude, Cursor, and every other AI tool, we build one MCP server that works everywhere.

As more AI tools adopt MCP, your Solenoid integration travels with you. No vendor lock-in to a specific assistant.

CI/Automation Use

For CI pipelines and automation, use an API key instead of OAuth:

export SOLENOID_API_KEY=sm_your_key_here
npx @solenoid.systems/mcp

Or pass it directly:

npx @solenoid.systems/mcp --api-key sm_your_key_here

Built-in Utilities

Every MCP installation includes:

• check_api_health — Verify API connectivity
• search_docs — Search Solenoid documentation
• list_docs — Browse available doc topics

Your AI assistant can look up how to use Solenoid without leaving the conversation.

What’s Next

This is v1.0. We’re planning:

• Resource subscriptions — Real-time updates when meters or flags change
• Batch operations — Process multiple requests in one call
• Custom prompts — Pre-built prompts for common workflows

Try It

If you have a Solenoid account:

npx @solenoid.systems/mcp

If you don’t:

# Sign up at solenoid.systems/pricing (free tier available)
# Then run the MCP server
npx @solenoid.systems/mcp

Your AI assistant just got access to edge infrastructure. Use it wisely.