MCP Factory

	User	Role	Created

	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.

Loading…

Help & Onboarding

What MCP Factory does

MCP Factory is the credential broker between your AI agents and the services they act on. Your agent authenticates to the gateway with one token; the gateway holds the real API keys and OAuth refresh tokens and hands the MCP servers only short-lived access tokens. You never paste a service credential into a client config, and you can rotate or revoke any token here without touching a single agent.

Get started in 5 steps

1

Create an API token

Go to API Tokens → + New Token. Give it a label naming where it will live (e.g. claude-desktop-laptop). The cgw_… value is shown once — copy it immediately. If you lose it, use Regenerate rather than creating a duplicate token.

2

Connect your services

Open MCP Servers and hit Configure on a server. Each server declares its own credential fields, so the modal renders exactly what that service needs — an API key, or a Connect button that runs the OAuth flow for Google, Microsoft, GoHighLevel, and friends. Credentials are stored in the gateway vault against your token, never in the MCP server and never on your machine.

3

Choose which servers and skill packs a token may reach

Your access comes from your roles (users with no role get the Default role), set by an admin on the Access tab. To narrow one token below that, use the Access action on its row in API Tokens. A token can only be narrowed, never widened. Give agents the narrowest set that still lets them do their job.

4

Connect Claude — HTTP connectors (no install)

Claude connects straight to the gateway over HTTP. Nothing runs on your machine. Add two connectors, both authenticated with your cgw_ token as Authorization: Bearer cgw_…:

MCP Factory: every server your token is entitled to, as tools.
Skills Factory: your skill packs (SOPs, playbooks), one tool per pack.

Loading…

claude.ai / Claude Desktop: Customize → Connectors → + → Add custom connector. Paste the URL, then under Request headers add 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.

Or let Claude Code wire it up: paste the prompt below into a Claude Code session. It adds both connectors, verifies them, and troubleshoots on its own.

Skills plugin (admins only for now)

Claude Desktop / claude.ai: Customize → Plugins → upload this file. It syncs to Claude Code on the same account. Uploads do not auto-update; download again after your skills or entitlements change.

Loading…

Paste it into a Claude Code session, then replace the token placeholder.

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.

5

Verify it works

Back in MCP Servers, use Test on a configured server to confirm the gateway can broker its credential. Then ask Claude to list its tools. With the recommended collapsed URL you get one tool per server (e.g. gohighlevel) plus one per skill pack; the flat URL (/mcp without ?surface=collapsed) lists every tool as <server>__<tool>. The API Tokens stats at the top of the dashboard tick up as calls flow through.

Install the mcpfactory plugin (Skills Factory slash commands)

One plugin, mcpfactory, holds every Skills Factory skill (about 568) as a slash command. Commands are named /mcpfactory:<pack>-<skill>, for example /mcpfactory:design-titanium-ui-retrofit. Each command loads the live skill from the store through the MCP Factory connector at run time, so skill edits are live with no reinstall. New or renamed skills arrive when the plugin repo re-syncs.

Prerequisite: the MCP Factory connector must be connected in your Claude account (see step 4 above).
Repo: finedesignz/mcpfactory-marketplace is a private GitHub repo. Your GitHub account needs read access to it.

Claude desktop and claude.ai web

Open Customize > Plugins > Add > Add marketplace > Add from a repository.
Click Install the Claude GitHub App and grant access to finedesignz/mcpfactory-marketplace.
Enter finedesignz/mcpfactory-marketplace.
Leave Sync automatically on.
Click Sync.
Install the mcpfactory plugin from it.

Claude Code CLI

claude plugin marketplace add finedesignz/mcpfactory-marketplace
claude plugin install mcpfactory@mcpfactory-marketplace

Enable auto-update: run /plugin, open Marketplaces, select it, then Enable auto-update. It is off by default for third-party marketplaces.
A private repo needs a git credential. Run gh auth login, then gh auth setup-git.
Updates apply about 10 minutes after the first message of a new session, or right away with claude plugin update mcpfactory@mcpfactory-marketplace.

Migrating from the old setup

If you have the old mcpfactory@local-desktop-app-uploads (a stale snapshot), uninstall it and install from the new marketplace. In the CLI:

claude plugin uninstall mcpfactory@local-desktop-app-uploads

In Claude desktop, remove it in the Plugins screen. Then follow the install steps above.

Plugin troubleshooting

"Repository not accessible" -- the Claude GitHub App lacks access to finedesignz/mcpfactory-marketplace. Grant it access and sync again.
A command is missing -- run Check for updates on the marketplace, or claude plugin marketplace update mcpfactory-marketplace.
Desktop is stuck on an old version -- a known upstream bug (anthropics/claude-code issues 45810 and 72089). Remove and re-add the marketplace.
A command exists but fails to load -- the MCP Factory connector is not connected or needs reconnecting.

By design, /mcpfactory:run <pack:skill> runs any store skill live, including ones added after the plugin was last synced.

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 Authorization header.
404 on /mcp or /skills/mcp — that endpoint isn't switched on for this deployment yet (RMT_ENABLED / SKILLS_MCP_ENABLED). Ask your admin; the Settings → Remote MCP card shows the status.
Skills Factory shows 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.
integration_disconnected — that service's OAuth grant was revoked upstream. Re-run Configure → Connect on the server.
401 from the gateway — the token was revoked, rotated, or truncated on paste, or the header value is missing the Bearer prefix. Reissue it and update the connector.
Server shows stale — it stopped heartbeating (5 min interval, flagged after 24h). It is never auto-deleted; check the server's deployment.
Mutations blocked / license required — renew in the Titanium portal, then reload this page.