| Name | Owner | Usage | Last used |
|---|
| User | Role | Created |
|---|
The skills library is not enabled on this gateway.
| Name | Details | Updated |
|---|
Suggestions
| Skill | Type | Submitted |
|---|
Roles
Roles grant MCP servers and skill packs. A user with no role gets the Default role. A custom per-user list overrides roles. Token owners can then narrow each token further from the API Tokens tab.
| Role | Description | Servers | Packs | Users |
|---|
User access
| User | Roles | Servers | Packs | Source |
|---|
Activity
Who changed roles, user access, token access and skills. Newest first.
| When | By | Area | Change |
|---|
Live inventory of MCP servers that self-registered with the gateway. Servers heartbeat every 5 min; flagged stale after 24h of silence (never auto-deleted). Force-delete to release a squatted name and revoke its token.
Remote MCP (HTTP connectors)
The default way to connect Claude (claude.ai, Desktop, mobile, Claude Code) and
cloud/scheduled agents: two HTTP endpoints + one of your gateway tokens. No local
install. See docs/remote-mcp.md.
Help & Onboarding
What MCP Factory does
MCP Factory is the credential broker between your AI agents and the services they act on.
Your agent connects to one connector URL with one token; the gateway
holds the real API keys and OAuth refresh tokens. Your skill packs (SOPs, playbooks) come through the
same connector as a skills tool, so there is nothing separate to connect.
Get started in 4 steps
Create an API token
Go to API Tokens -> + New Token and label it for where it will live
(e.g. codex-laptop). The cgw_... value is shown once;
if you lose it, use Regenerate. What a token can reach comes from your roles
(Access tab); use the Access action on a token row to narrow it further.
Connect your services
Open MCP Servers and hit Configure on a server: paste an API key or click Connect to run its OAuth flow. Credentials stay in the gateway vault, never on your machine.
Connect your agent
One connector URL, authenticated with your token as Authorization: Bearer cgw_...
(Streamable HTTP, nothing to install):
Loading...
Any MCP-capable agent (Codex, Cursor, Windsurf, ChatGPT/OpenAI agents, Claude, or a generic client): paste this prompt into the agent, then replace the token placeholder.
Loading...
claude.ai / Claude Desktop: Customize -> Connectors -> + -> Add custom
connector. Paste the URL, keep Authentication -> Sign in now and
OAuth client -> Use Claude's published identity, then click Connect and approve
on the MCP Factory sign-in page. (Fallback: No sign-in plus a Request header
Authorization = Bearer cgw_....) Connectors added on claude.ai also show
up in Claude Desktop and mobile. Remote URLs do not go in
claude_desktop_config.json; that file only holds local (stdio) servers.
Claude Code: run the command below, or paste the prompt.
Loading...
Your cgw_ token is a live credential. The snippets ship with a placeholder.
Swap in your real token locally, and don't paste it into a shared chat or commit it.
Verify it works
Ask the agent to list its tools. You should see one tool per server you can reach
(e.g. gohighlevel) plus skills. An empty list is a failure; see
troubleshooting below. In MCP Servers, Test confirms the gateway can
broker a server's credential.
Claude Code only (optional): skills as slash commands
A plugin adds one slash command per skill; each loads the live skill through the connector above, so
connect that first. Requires read access to the private GitHub repo
finedesignz/mcpfactory-marketplace (run gh auth login, then gh auth setup-git).
/plugin marketplace add finedesignz/mcpfactory-marketplace /plugin install mcp-factory-skills@mcpfactory-marketplace
Use /mcp-factory-skills:run <pack:skill> to run any skill. If commands go missing,
run /plugin marketplace update mcpfactory-marketplace.
Troubleshooting
- Agent sees no tools — the token's access (roles, or its own Access scope) excludes every server, or the connector was added without the
Authorizationheader. - 401 from the gateway — the token was revoked, rotated, or truncated on paste, or the header value is missing the
Bearerprefix. Reissue it and update the connector. - 404 on
/mcp-- that endpoint isn't switched on for this deployment yet (RMT_ENABLED). Ask your admin; the Settings -> Remote MCP card shows the status. skillstool lists no packs -- the token is a server/service identity or has no owner, or its access excludes every pack. Use a personal token created under your own login.permission_error: ... user:mcp_serversfrom a subagent using a connector synced from claude.ai (claude_ai_<label>in Claude Code) -- this comes from the Claude host's own OAuth session, not MCP Factory. Add the direct connector with the Claude Code command above instead.integration_disconnected-- that service's OAuth grant was revoked upstream. Re-run Configure -> Connect on the server.- Mutations blocked / license required — renew in the Titanium portal, then reload this page.