Resourced PLM connector
Give an AI assistant access to your PLM: ask it about a brand's catalogue, and let it make changes through a curated, approved slice of the API.
The address
https://mcp.resourced.com/mcp
This connector reads and writes
live production data
at https://app.resourced.com. You sign in with your own PLM account, and it can
only reach the brands your account can.
Adding it
Claude (claude.ai and the desktop app)
Settings → Connectors → Add custom connector, and paste the address above. Claude opens a page asking you to approve the connection; if you are already signed in to the PLM in that browser, that is the whole of it.
On a Team or Enterprise plan an owner can add it once under Organization settings → Connectors, and everyone else simply clicks Connect.
Claude Code
claude mcp add --transport http resourced https://mcp.resourced.com/mcp
Then /mcp in a session to sign in.
Codex
codex mcp add resourced --url https://mcp.resourced.com/mcp codex mcp login resourced
ChatGPT
Settings → Apps → enable developer mode, then add the address above as a custom connector.
Anything else
A client that speaks MCP over HTTP takes the address directly. One that only speaks stdio can reach it through a shim:
npx -y mcp-remote https://mcp.resourced.com/mcp
What it can do
9 tools. Your client can approve them separately — the ones that only read are safe to leave on.
| Tool | What it is | |
|---|---|---|
list_brands | List brands | reads only |
search_api | Search the API and docs | reads only |
get_brand_context | Read brand configuration | reads only |
read | Ask a question | reads only |
run | Run a change | changes data |
dry_run | Rehearse a change (dry run) | reads only |
request_upload | Request an upload link | creates |
check_upload | Check an upload | reads only |
report_gap | Report a gap to the maintainers | creates |
Scripts run in a sandbox with no network, no secrets and no filesystem beyond its own code, and may only call 815 endpoints that have been reviewed and approved for agent use. Everything else is refused before the request is built.
Signing in, and signing out
Approving the connection creates an API key for that connection alone, named after the client that asked and valid for 365 days. It stays on this server, bound to the token your client holds; the client never sees it, and nothing is shared with your other integrations.
Every connection is listed under API Keys in the PLM. Revoking one ends that connection and no other, and each key expires on its own even if nobody revokes it.
Build 2026-10-30.