Add Directory MCP server to marketplaces

[adamtagscherer]

Make Agent Directory MCP server available in Cursor, Claude Code and VS Code.

The main goal with this mini epic is to provide a zero configuration, UI based solution for easy install process for different IDEs.

[arpad-csepi]

Publishing the Directory MCP Server

The recommended approach is to publish once to the Official MCP Registry (registry.modelcontextprotocol.io). This is the canonical, machine-readable catalog maintained by the MCP Steering Committee. Publishing there propagates automatically to downstream directories (Glama, mcp.so, PulseMCP) which serve all three target platforms.

Alternatively, you can submit directly to platform-specific or community registries without using the Official Registry.

---

Option 1: Official MCP Registry (recommended)

Publishing here is the highest-leverage action. It requires no npm/PyPI package — the registry is metadata-only and points to the existing Docker image.

Prerequisites

Install the mcp-publisher CLI:

brew install mcp-publisher
# or download from https://github.com/modelcontextprotocol/registry/releases

Step 1 — Add server.json to the repository root

{
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "name": "io.github.agntcy/dir-mcp",
  "description": "MCP server for working with OASF agent records in the Agntcy Directory.",
  "repository": {
    "url": "https://github.com/agntcy/dir-mcp",
    "source": "github"
  },
  "version": "1.0.0",
  "packages": [
    {
      "registryType": "docker",
      "identifier": "ghcr.io/agntcy/dir-ctl",
      "version": "latest",
      "transport": { "type": "stdio" },
      "environmentVariables": [
        {
          "name": "OASF_API_VALIDATION_SCHEMA_URL",
          "description": "OASF schema server URL (e.g. https://schema.oasf.outshift.com)",
          "isRequired": true,
          "isSecret": false
        },
        {
          "name": "DIRECTORY_CLIENT_SERVER_ADDRESS",
          "description": "Directory server address (default: 0.0.0.0:8888)",
          "isRequired": false,
          "isSecret": false
        },
        {
          "name": "DIRECTORY_CLIENT_AUTH_MODE",
          "description": "Auth mode: none, github, x509, jwt, token",
          "isRequired": false,
          "isSecret": false
        },
        {
          "name": "DIRECTORY_CLIENT_GITHUB_TOKEN",
          "description": "GitHub PAT for github auth mode",
          "isRequired": false,
          "isSecret": true
        }
      ]
    }
  ]
}

Step 2 — Authenticate and publish

mcp-publisher login github   # opens a browser device-code flow
mcp-publisher publish

Expected output:

✓ Server io.github.agntcy/dir-mcp version 1.0.0

Step 3 — Automate with GitHub Actions (optional)

Add the following to your release workflow to publish automatically on every tagged release. It uses GitHub OIDC so no secrets are required:

- name: Publish to MCP Registry
  uses: modelcontextprotocol/registry/.github/actions/publish@main
  with:
    server-path: server.json
  permissions:
    id-token: write

What this unlocks

Platform	How it becomes available
VS Code	Surfaced in VS Code Insiders via the @mcp Extensions search. VS Code Stable support is in active development.
Claude Code	Discoverable via MCPfinder and Glama/mcp.so, which auto-ingest the Official Registry within a few days of publishing.
Cursor	Discoverable via Glama, mcp.so, and Smithery, all of which auto-ingest the Official Registry and generate ready-to-paste Cursor config snippets.

---

Option 2: Smithery

Smithery is a third-party registry that generates per-client one-click install configs for Claude Code, Cursor, Cline, and Windsurf. It is useful if you want hosted (cloud-run) deployment or polished per-client install buttons.

Add smithery.yaml to the repository root

startCommand:
  type: stdio

configSchema:
  type: object
  required:
    - oasfSchemaUrl
  properties:
    oasfSchemaUrl:
      type: string
      description: "OASF schema server URL (e.g. https://schema.oasf.outshift.com)"
    directoryAddress:
      type: string
      default: "0.0.0.0:8888"
      description: "Directory server address"
    authMode:
      type: string
      default: "none"
      description: "Auth mode: none, github, x509, jwt, token"
    githubToken:
      type: string
      description: "GitHub PAT (required when authMode is github)"

commandFunction: |-
  (config) => ({
    command: 'docker',
    args: ['run', '--rm', '-i', 'ghcr.io/agntcy/dir-ctl:latest', 'mcp', 'serve'],
    env: {
      OASF_API_VALIDATION_SCHEMA_URL: config.oasfSchemaUrl,
      DIRECTORY_CLIENT_SERVER_ADDRESS: config.directoryAddress || '0.0.0.0:8888',
      ...(config.authMode && { DIRECTORY_CLIENT_AUTH_MODE: config.authMode }),
      ...(config.githubToken && { DIRECTORY_CLIENT_GITHUB_TOKEN: config.githubToken })
    }
  })

Note: configSchema must be a plain JSON Schema object. Zod wrappers (z.object()) are not supported and are the most common cause of Smithery deployment failures.

Submit to Smithery

Go to smithery.ai/new and enter the GitHub repository URL. Smithery reads smithery.yaml from the default branch.

---

Option 3: Glama

Glama is a large third-party MCP directory (~19,000 servers) with its own submission pipeline and build verification. It is worth submitting to directly because:

• It issues a Glama badge that awesome-mcp-servers requires before accepting a PR.
• It runs build verification on submitted servers and flags configuration issues.
• It generates ready-to-paste install configs for Cursor, Claude Code, and other clients.

Glama also auto-ingests from the Official Registry (Option 1), so if you have already published there, no separate submission is needed — Glama will pick it up automatically within a few days.

Direct submission

If you want to appear on Glama before or without publishing to the Official Registry, submit a PR to the Glama MCP servers repository with your server metadata.

Once listed, add the badge to your README.md:

[![Glama Badge](https://glama.ai/mcp/servers/badge/@agntcy/dir-mcp)](https://glama.ai/mcp/servers/@agntcy/dir-mcp)

The badge is required to be accepted by awesome-mcp-servers, which has 80k+ GitHub stars and is a major discovery surface.

---

Option 4: Community directories (no tooling required)

These require no manifest files or CLI — just a web form or pull request.

Directory	Submission	Notes
cursor.directory	Web form	Community-driven listing for Cursor users.
awesome-mcp-servers	PR to the repo	Requires a Glama badge (see Option 3).
mcp.so	Auto-ingested from Official Registry	No separate submission needed after Option 1.

---

Platform-specific notes

Cursor

Cursor does not have an open developer submission portal for its in-app marketplace. The Cursor Team Marketplace (v3.10+) is for Teams/Enterprise admins to distribute pre-approved servers internally — it is not a public channel.

For community discoverability, the Official Registry and cursor.directory are the practical paths.

Claude Code

Claude Code has no separate registry. Users install MCP servers via:

claude mcp add dir-mcp docker run --rm -i ghcr.io/agntcy/dir-ctl:latest mcp serve

Registries like Smithery and MCPfinder generate these commands automatically once the server is listed.

VS Code

VS Code 1.99+ has native MCP support. The Official Registry is already surfaced in VS Code Insiders under the @mcp tag in the Extensions view. Full integration into VS Code Stable is in development.

The GitHub MCP Registry (surfaced in GitHub Copilot) is a curated list managed by GitHub — there is no self-service submission portal.