Portkey Admin MCP vs Replicate
A side-by-side look at the Portkey Admin MCP and Replicate MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Portkey Admin MCP for conversational ai work as a local process; choose Replicate for conversational ai as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Portkey Admin MCP when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PORTKEY_API_KEY. - You want tools like
list_all_users, invite_user, get_user_stats.
Choose Replicate when
- You need dedicated capabilities in the Conversational AI domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_REPLICATE_KEY. - You want tools like
list_models, model, model_versions.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Conversational AI | Conversational AI |
| Quality signal | 65/100 · Great | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | PORTKEY_API_KEY | PLATFORM_REPLICATE_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 184 | 16 |
| Full listing | View Portkey Admin MCP | View Replicate |
Tools & capabilities
Portkey Admin MCP tools 184
list_all_usersList accepted org users with id, name, email, role, and timestamps. Use this to find a user_id before get_user, update_user, delete_user, or add_workspace_member; use list_user_invites for pending invitations. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.invite_userInvite a new org user and optionally provision workspace access and an API key in one call. Workspace assignments apply only after acceptance; use add_workspace_member or update_workspace_member later for follow-up changes.get_user_statsReturn per-user request and cost analytics for a required time range. This is usage-by-user, not population metrics; use get_users_analytics for active-user or cohort trends. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.get_userGet one accepted user by id and return their profile, role, and timestamps. Use list_all_users to find the id if you only have a name or email, and get_user_invite for pending invitations. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.update_userUpdate a user's first name, last name, or organization role by id. Email and workspace roles are not editable here; use update_workspace_member for workspace membership changes.delete_userDelete a user from the org by id. This is permanent, removes org and workspace memberships, revokes API keys, and ends active sessions; use delete_user_invite for pending invites instead.list_user_invitesList pending and sent invitations with id, email, role, status, and expiry. Use this to check invite state; use list_all_users for users who already accepted. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.get_user_inviteGet one invitation by invite id and return its email, role, status, and expiry. Use this for pending invites only; use get_user for accepted users.delete_user_inviteDelete a pending invite and revoke its invite link. This does not affect existing users; use delete_user for full user removal.resend_user_inviteResend the email for a pending invite that has not been accepted, unlike invite_user which creates a new invite. This sends a fresh email without modifying the invite record, expiry, or role; use get_user_invite first if you are unsure whether the invite still exists and list_user_invites to discover invite_ids.list_scim_workspace_mappingsList identity-provider SCIM group mappings that automatically grant Portkey workspace roles. Use it to audit provisioned access or obtain mapping_id before delete_scim_workspace_mapping; filter by workspace, group, or role and page through large directories. This reads mappings only and does not query individual workspace members. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.create_scim_workspace_mappingMap one identity-provider SCIM group to a Portkey workspace role so current and future group members receive access automatically. Provide exactly one of scim_group_id or scim_group_name; a name can pre-create the Portkey SCIM group before the IdP provisions it. Use list_scim_groups to discover existing groups and list_workspaces for the workspace ID. This changes access provisioning and is distinct from add_workspace_member, which grants one user directly. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans.- +172 more on the listing page
Replicate tools 16
list_modelsList all public models available on Replicate, paginated via cursor; returns owner, name, description, run count, and latest version id for each model.modelFetch metadata for a specific Replicate model by owner and name, including description, visibility, run count, latest version, and GitHub URL.model_versionsList all published versions of a Replicate model by owner and name; returns version ids, creation timestamps, and input/output schema for each version.model_versionFetch full metadata for a specific Replicate model version by owner, name, and version_id, including the complete input/output OpenAPI schema and Cog version.search_modelsSearch public Replicate models by keyword query; returns matching models with owner, name, description, and run count.collectionsList all curated Replicate model collections (e.g. "text-to-image", "speech-to-text"); returns collection slug, name, and description.collectionFetch models belonging to a specific Replicate collection by slug (e.g. "text-to-image"); returns the collection description and a list of model objects.create_predictionStart a Replicate model run by submitting a version id and input object; returns a prediction id and status that can be polled with the prediction tool until output is ready.predictionPoll the status and retrieve output for a Replicate prediction by id; returns status (starting/processing/succeeded/failed/canceled), output URLs, and logs.list_predictionsList your recent Replicate predictions in reverse chronological order, paginated via cursor; returns prediction id, model version, status, and creation timestamp.cancel_predictionCancel a prediction.list_deploymentsList your Replicate model deployments (dedicated, auto-scaled endpoints), paginated via cursor; returns owner, name, current model version, and scaling config.- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Portkey Admin MCP
{
"mcpServers": {
"portkey-admin-mcp": {
"command": "npx",
"args": [
"-y",
"portkey-admin-mcp"
],
"env": {
"PORTKEY_API_KEY": "YOUR_PORTKEY_API_KEY_HERE"
}
}
}
}
Replicate
{
"mcpServers": {
"replicate": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-replicate"
],
"env": {
"PLATFORM_REPLICATE_KEY": "YOUR_PLATFORM_REPLICATE_KEY_HERE"
}
}
}
}
Frequently asked questions
Portkey Admin MCP is categorized under Conversational AI and uses a local stdio subprocess. Replicate belongs to Conversational AI and uses a local stdio subprocess. Pick Portkey Admin MCP for conversational ai work and Replicate for conversational ai.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Portkey Admin MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Replicate has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add portkey-admin-mcp and replicate as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Portkey Admin MCP has a quality signal of 65/100 (Great) with 2 views, 0 installs and 6 GitHub stars. Replicate has 56/100 (Good) with 1 views, 0 installs and 0 GitHub stars.