Claude Code

Claude Code adds remote MCP servers from the command line. One command, then sign in.

One command

claude mcp add --transport http onlyx https://mcp.onlyx.ai/mcp

To make OnlyX available in all your projects rather than only the current one, add --scope user:

claude mcp add --transport http onlyx https://mcp.onlyx.ai/mcp --scope user

Start Claude Code and run:

/mcp

Select onlyx, choose Authenticate, and your browser opens OnlyX. Sign in, choose the workspace, and click Approve. Back in the terminal, /mcp shows OnlyX as connected. Claude Code refreshes the sign-in automatically from then on. Check it: “Which OnlyX workspace am I connected to?”

Use an API key instead

For a read-only assistant, scripts, or machines without a browser, pass an API key as a header:

export ONLYX_API_KEY="onx_sk_..."   # a Read only key keeps Claude Code read-only
claude mcp add --transport http onlyx https://mcp.onlyx.ai/mcp --scope user \
  --header "Authorization: Bearer $ONLYX_API_KEY"

Your shell expands $ONLYX_API_KEY when you run the command, so the key is saved in your Claude Code configuration (~/.claude.json). To keep only a reference to the environment variable instead, add it as JSON with single quotes:

claude mcp add-json onlyx '{"type":"http","url":"https://mcp.onlyx.ai/mcp","headers":{"Authorization":"Bearer ${ONLYX_API_KEY}"}}' --scope user

Where the configuration lives

`--scope`	Stored in	Who gets it
`local` (default)	`~/.claude.json`, for the current project	Only you, only in this project
`user`	`~/.claude.json`	Only you, in every project
`project`	`.mcp.json` in the repository	Everyone who works in the repository

To give everyone working in a repository the OnlyX server, commit a .mcp.json:

.mcp.json

{
  "mcpServers": {
    "onlyx": {
      "type": "http",
      "url": "https://mcp.onlyx.ai/mcp"
    }
  }
}

Each person signs in with their own OnlyX account through /mcp. If you prefer keys, add "headers": {"Authorization": "Bearer ${ONLYX_API_KEY}"} and have each person set ONLYX_API_KEY in their environment. Never commit a key itself.

Prompts as slash commands

OnlyX’s built-in workflows appear as slash commands:

/mcp__onlyx__daily_briefing
/mcp__onlyx__reply_to_unread_fans
/mcp__onlyx__onboard_a_creator
/mcp__onlyx__build_ai_persona
/mcp__onlyx__build_content_ladder
/mcp__onlyx__weekly_revenue_report

See Using OnlyX with Claude for what each does.

Tool permissions

Claude Code asks before it runs a tool. You can pre-approve read tools you use often (for example mcp__onlyx__get_today_stats or mcp__onlyx__list_conversations) in your Claude Code permission settings. Keep the tools that reach fans (mcp__onlyx__send_message, mcp__onlyx__update_creator, mcp__onlyx__release_conversation, mcp__onlyx__set_conversation_ai, mcp__onlyx__resolve_handoff, mcp__onlyx__update_ai_settings, mcp__onlyx__update_welcome_message, mcp__onlyx__create_tracking_link) on ask.

Manage the server

claude mcp list          # all servers and their status
claude mcp get onlyx     # details for OnlyX
claude mcp remove onlyx  # remove it (add --scope user if you added it there)

Troubleshooting

Problem	Fix
`/mcp` shows OnlyX as needing authentication	Select it and choose Authenticate again.
”Unauthorized” with a key	The key is wrong, revoked or expired, or `ONLYX_API_KEY` was empty when you ran `claude mcp add`. Remove the server and add it again.
The browser sign-in does not return to the terminal	Finish the approval in the browser, then run `/mcp` again. If a firewall blocks local callbacks, use an API key.
OnlyX tools are missing in a project	You added it with the default `local` scope in another project. Add it with `--scope user`.

Using OnlyX with Claude: recipes and safety habits.
Tools: every tool name (prefixed mcp__onlyx__ in Claude Code).

MCP server

Connect your assistant

Reference

One command

Use an API key instead

Where the configuration lives

Prompts as slash commands

Tool permissions

Manage the server

Troubleshooting

Next

​One command

​Sign in

​Use an API key instead

​Where the configuration lives

​Share with your team

​Prompts as slash commands

​Tool permissions

​Manage the server

​Troubleshooting

​Next

One command

Sign in

Use an API key instead

Where the configuration lives

Share with your team

Prompts as slash commands

Tool permissions

Manage the server

Troubleshooting

Next