add-mcp-integration skillA
add-mcp-integration is agent-read markdown (skill) from vellum-ai/vellum-assistant: Add a vendor's remote MCP server to the bundled integrations catalog (plugins/mcp-catalog/<name>/ + plugins/marketplace.json) so users can connect it from the Integrations page. Covers vetting the server's OAuth support, the icon, the package files, the generators, the CI checks, and the PR. Use when asked to "add <vendor> MCP", "add <vendor> to integrations", or to check whether a vendor's MCP server is an easy addition..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Add an MCP Integration A catalog integration is a bundled local plugin whose only content is an `mcp.json` pointing at the vendor's remote server. The assistant ships it, the Integrations page lists it, and connecting it runs the MCP OAuth flow in `assistant/src/mcp/mcp-oauth-provider.ts`. Scope: remote MCP servers in `plugins/mcp-catalog/`. For a full plugin that lives in another GitHub repo, see `plugins/README.md` § Marketplace. Work in a worktree from `origin/main`. One provider per PR. ## 1. Research the server From the vendor's MCP docs, record: - The remote URL. Prefer `streamable-http` (docs often say `"type": "http"`). - The docs page URL. It is both `homepage` and `documentationUrl`. - A one-line summary of what the tools do. Reject a server that only runs locally (`npx`, `uvx`, Docker). The catalog ships no stdio servers. ## 2. Check OAuth support The catalog's one-step connect needs the server to support OAuth discovery and dynamic client registration (DCR), because a plugin cannot ship a client secret. ```bash URL=https://mcp.example.com/mcp curl -sS -i -X POST "$URL" -H 'content-type: application/json' \ …
Read the whole file at its exact version.
How to install
mdr add vellum-ai/vellum-assistant/add-mcp-integration@git:20260924.494829cmdr add vellum-ai/vellum-assistant/add-mcp-integration@sha256:07544c74ea22edb8Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_2n2ru46loyffzjop)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11284 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vellum-ai/vellum-assistant · 1,314 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2n2ru46loyffzjop GET https://markdownregistry.com/api/v1/resolve?ref=vellum-ai/vellum-assistant/add-mcp-integration GET https://markdownregistry.com/api/v1/blob/07544c74ea22edb85628da57dc7937cf1445570c2129c02cb05ebede17e9174c
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.