English Français العربية

ai.packmind/mcp-server

Official registry Other

Packmind captures, scales, and enforces your organization's technical decisions.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http ai-packmind-mcp-server 'https://app.packmind.ai/mcp' --header 'Authorization: <Bearer token for Packmind authentication>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "ai-packmind-mcp-server": {
            "type": "http",
            "url": "https://app.packmind.ai/mcp",
            "headers": {
                "Authorization": "<Bearer token for Packmind authentication>"
            }
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. One Engineering Playbook. Synced Everywhere. For Every AI Coding Agent.
  2. 🆚 Why Packmind over a plain Claude Code marketplace or a plain centralized Git repository?
  3. Get started
  4. Option 1: Install the CLI (recommended)
  5. Documentation
  6. :compass: Key Links

One Engineering Playbook. Synced Everywhere. For Every AI Coding Agent.

❗ The 2 big problems every AI-native engineer runs into

1️⃣ “What do I even put in these AI instructions?”

Every tool expects its own inputs:

  • Copilot → .github/copilot-instructions.md, chat modes, reusable prompts
  • Claude → CLAUDE.md, commands, skills
  • Cursor → .cursor/rules/*.mdc, commands, skills
  • AGENTS.md → AGENTS.md
  • (with more formats appearing every month…)

But your team’s actual standards aren’t stored anywhere:

  • architecture rules → buried in Slack or Notion
  • naming conventions → stuck in your head
  • patterns → hiding in PR comments
  • best practices → scattered across repos

👉 Packmind helps you turn all of this into a real engineering playbook (standards, commands, skills) so AI agents finally code your way.

2️⃣ “Why am I copy-pasting this across every repo and every agent?”

Every repo. Every assistant. Different files, different folders, different formats.

Keeping everything in sync is impossible.

👉 Packmind centralizes your playbook once — and distributes it everywhere, generating the exact instruction files each AI tool needs, optimized for context.

🆚 Why Packmind over a plain Claude Code marketplace or a plain centralized Git repository?

A marketplace distributes skills and commands from a Git repo. Packmind does more:

  • Controlled editing: context files go through a clear ownership and approval workflow. No PR discipline or CODEOWNERS conventions to enforce.
  • Simplified updates: update proposals are submitted from the project codebase, no separate repo to clone or PR.
  • Multi-agent: one source, rendered for Claude Code, Copilot, Cursor and more. No parallel CLAUDE.md or .cursor/rules to maintain.
  • Adoption tracking: see which context files are used, in which repo, at which version.

A marketplace ships content. Packmind governs it.

Get started

Choose your preferred setup option:

Follow the instructions during the onboarding to connect to your Packmind organization You can find them at anytime in the Settings menu.

Once authenticated, run in your project:

$> packmind init

Then, in your favorite ai coding agent, run:

/packmind-onboard

To create your first standards and commands from your codebase.

Documentation

Available here: https://docs.packmind.com.

Frequently asked questions

What is ai.packmind/mcp-server?

Packmind captures, scales, and enforces your organization's technical decisions.

How do I install ai.packmind/mcp-server?

It runs as a remote server. In Claude Code: claude mcp add --transport http ai-packmind-mcp-server 'https://app.packmind.ai/mcp' --header 'Authorization: <Bearer token for Packmind authentication>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does ai.packmind/mcp-server need an API key?

Yes. It expects Authorization, which you set in its configuration.

Is ai.packmind/mcp-server open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains ai.packmind/mcp-server?

It is published by PackmindHub. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.