Connect BlackOps to your AI client
The BlackOps MCP server is how your AI client reads and writes your content. Connecting it is the one step that turns BlackOps on. Pick your client below and follow the steps.
Fastest path: let the agent set it up
If you use Claude Code, one command installs the connector and walks you through your first publish. No config files, no token to copy.
npx blackops-onboard
Prefer to wire it up by hand? Use the per-client steps below.
What you need
Server URL
Paste this wherever your client asks for an MCP server URL.
https://mcp.blackopscenter.com/mcp
Authentication
Two ways to authenticate, depending on your client:
- Sign in (OAuth). Clients that support remote MCP (Claude Desktop, Claude on the web) open a browser to sign in at blackopscenter.com. Nothing to copy.
- Bearer token. Other clients use a token in an
Authorizationheader. Generate one under Admin → Settings.
Connect your client
- 1
Open Claude Desktop and go to Settings, then Developer, then Edit Config.
- 2
Add the "blackops" server to the mcpServers block (below), using a token from Admin → Settings.
- 3
Save the file and fully restart Claude Desktop.
{
"mcpServers": {
"blackops": {
"type": "url",
"url": "https://mcp.blackopscenter.com/mcp",
"headers": {
"Authorization": "Bearer YOUR_BLACKOPS_TOKEN"
}
}
}
}Verify it worked
Ask your AI client this, in plain language:
List my BlackOps sites.
If it lists your site (or sites), the connection is live and you can start publishing. If it cannot, double-check the URL and that your token is from Admin → Settings and has not expired.
Troubleshooting
Fully quit and reopen the client. Most clients only read MCP config on startup.
Your token is missing, wrong, or expired. Generate a fresh one under Admin → Settings and confirm the header reads Authorization: Bearer ....
That client expects a local (stdio) server. Use npx blackops-onboard for the guided local setup instead.