Strake
all systems normal sign in create your endpoint
sign in create your endpoint
all systems normal
mcp

Stop putting credentials
in your MCP config files.

MCP servers need API tokens for GitHub, Slack, databases, and dozens of other services. Right now those tokens sit in plaintext JSON on your machine. Strake replaces them with disposable URLs you can revoke anytime.

Create your first endpoint Read the docs
/01 the problem

Your MCP config is a credentials dump.

Open your claude_desktop_config.json or .cursor/mcp.json right now. How many real API tokens are in there? GitHub personal access tokens. Slack bot tokens. Database credentials. Each one in plaintext, on disk, in a file that's easy to accidentally commit, share, or leak. If your machine is compromised, every service in that config file is compromised with it.

/02 how it works

Two fields changed. Zero tokens exposed.

01

Store your real tokens in Strake

GitHub, Slack, Stripe, whatever your MCP servers need — encrypted in the vault, never on disk.

02

Put Strake URLs in your MCP config instead

The MCP server connects through Strake and never sees the real credential. Your config file is safe to share.

03

Revoke per-server, per-tool

Disconnect one MCP server without rotating credentials across everything else. Granular control, instant effect.

/03 the change

Two fields changed. Zero tokens exposed.

before real token in your MCP config
{
  "mcpServers": {
    "github": {
      "url": "https://mcp.github.com/sse",
      "headers": {
        "Authorization": "Bearer ghp_realGitHubToken..."
      }
    }
  }
}
after strake endpoint, token stays in the vault
{
  "mcpServers": {
    "github": {
      "url": "https://my-github.strake.sh/sse",
      "headers": {
        "Authorization": "Bearer ct_live_7a3f..."
      }
    }
  }
}
/04 use cases

What it makes possible.

Share your MCP setup safely

Export your config, share it with a teammate or post it in a guide. No real tokens exposed. They set up their own Strake endpoints for their own keys.

Try new MCP servers without risk

Experimenting with a community MCP server you don't fully trust? Give it a Strake token. If anything feels off, revoke it. Your real credentials were never exposed.

One dashboard for all your MCP credentials

GitHub, Slack, Linear, Sentry, databases — manage every MCP server's access from one place instead of scattered across config files.

/05 ship it

Connect MCP servers.
Keep credentials out of config files.

Two fields changed in your config. Your real tokens stay in the vault. Revoke any server in seconds.

Get started Read the docs