Flagsmith

Model Context Protocol (MCP) Server for the flagsmith API.

Built by Speakeasy License: MIT

[!IMPORTANT] This MCP Server is not yet ready for production use. To complete setup please follow the steps outlined in your workspace. Delete this notice before publishing to a package manager.

Summary

mcp_openapi: Flagsmith's Core and SDK APIs. Check out Flagsmith documentation.

Table of Contents

• flagsmith
  • Installation
  • Progressive Discovery
  • Development
  • Publishing to Anthropic MCP Registry
  • Contributions

Installation

[!TIP] To finish publishing your MCP Server to npm and others you must run your first generation action.

{
  "command": "npx",
  "args": [
    "flagsmith",
    "start",
    "--token-auth",
    ""
  ]
}

claude mcp add Flagsmith -- npx -y flagsmith start --token-auth 

gemini mcp add Flagsmith -- npx -y flagsmith start --token-auth 

{
  "command": "npx",
  "args": [
    "flagsmith",
    "start",
    "--token-auth",
    ""
  ]
}

{
  "command": "npx",
  "args": [
    "flagsmith",
    "start",
    "--token-auth",
    ""
  ]
}

npx flagsmith start --token-auth 

npx flagsmith --help

Progressive Discovery

MCP servers with many tools can bloat LLM context windows, leading to increased token usage and tool confusion. Dynamic mode solves this by exposing only a small set of meta-tools that let agents progressively discover and invoke tools on demand.

To enable dynamic mode, pass the --mode dynamic flag when starting your server:

{
  "mcpServers": {
    "Flagsmith": {
      "command": "npx",
      "args": ["flagsmith", "start", "--mode", "dynamic"],
      // ... other server arguments
    }
  }
}

In dynamic mode, the server registers only the following meta-tools instead of every individual tool:

• list_tools: Lists all available tools with their names and descriptions.
• describe_tool: Returns the input schema for one or more tools by name.
• execute_tool: Executes a tool by name with the provided input parameters.

This approach significantly reduces the number of tokens sent to the LLM on each request, which is especially useful for servers with a large number of tools.

Development

Run locally without a published npm package:

1. Clone this repository
2. Run npm install
3. Run npm run build
4. Run node ./bin/mcp-server.js start --token-auth To use this local version with Cursor, Claude or other MCP Clients, you'll need to add the following config:

{
  "command": "node",
  "args": [
    "./bin/mcp-server.js",
    "start",
    "--token-auth",
    ""
  ]
}

Or to debug the MCP server locally, use the official MCP Inspector:

npx @modelcontextprotocol/inspector node ./bin/mcp-server.js start --token-auth 

Publishing to Anthropic MCP Registry

To publish your MCP server to the Anthropic MCP Registry, follow these steps based on the official publishing guide.

Step 1: Configure mcpName in Your Generation Config

Add the mcpName field to your .speakeasy/gen.yaml file:

mcp-typescript:
  mcpName: io.github.username/server-name  # Use reverse-DNS format
  # ... other configuration

The mcpName should follow the reverse-DNS format (e.g., io.github.username/server-name) to ensure uniqueness in the registry.

Step 2: Regenerate Your MCP Server

Run Speakeasy generation with the updated configuration. This will:

• Add the mcpName field to your package.json (required for npm package validation)
• Generate a server.json file with registry metadata

Step 3: Publish to npm

The registry validates npm packages by checking that your published package includes the mcpName field:

npm publish

The registry will fetch your package from npm and verify that the mcpName in package.json matches your server name.

Step 4: Install the Publisher CLI

Install the mcp-publisher CLI tool:

macOS/Linux (Homebrew):

brew install mcp-publisher

macOS/Linux/WSL (curl):

curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher && sudo mv mcp-publisher /usr/local/bin/

Windows PowerShell:

$arch = if ([System.Runtime.InteropServices.RuntimeInformation]::ProcessArchitecture -eq "Arm64") { "arm64" } else { "amd64" }
Invoke-WebRequest -Uri "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_windows_$arch.tar.gz" -OutFile "mcp-publisher.tar.gz"
tar xf mcp-publisher.tar.gz mcp-publisher.exe
rm mcp-publisher.tar.gz
# Move mcp-publisher.exe to a directory in your PATH

Step 5: Authenticate

Authenticate based on your namespace:

For io.github.* namespaces (GitHub OAuth):

mcp-publisher login github

For custom domains like com.yourcompany.* (DNS authentication):

# Generate keypair
openssl genpkey -algorithm Ed25519 -out key.pem

# Get public key for DNS record
echo "yourcompany.com. IN TXT \"v=MCPv1; k=ed25519; p=$(openssl pkey -in key.pem -pubout -outform DER | tail -c 32 | base64)\""

# Add the TXT record to your DNS, then login
mcp-publisher login dns --domain yourcompany.com --private-key $(openssl pkey -in key.pem -noout -text | grep -A3 "priv:" | tail -n +2 | tr -d ' :\n')

Step 6: Publish to the Registry

From your server directory, publish to the registry:

mcp-publisher publish

You'll see:

✓ Successfully published

Step 7: Verify Publication

Check that your server appears in the registry:

curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.username/server-name"

For complete documentation including remote deployments, troubleshooting, and CI/CD automation, see the official publishing guide.

Contributions

While we value contributions to this MCP Server, the code is generated programmatically. Any manual changes added to internal files will be overwritten on the next generation. We look forward to hearing your feedback. Feel free to open a PR or an issue with a proof of concept and we'll do our best to include it in a future release.

MCP Server Created by Speakeasy