Open Source · MIT · v0.2

Install AI skills once.
Available everywhere.

AMP is a package manager for MCP servers. Run amp add once — it writes native config into Claude Code, Cursor, VS Code, JetBrains, Warp, and Claude Desktop. No copy-paste. No drift.

Get Started Star on GitHub

Written in Rust Zero dependencies macOS · Linux · Windows

~/projects/my-app — amp

irm https://github.com/ShadowsKeep/amp/releases/latest/download/install.ps1 | iex

curl -fsSL https://github.com/ShadowsKeep/amp/releases/latest/download/install.sh | bash

cargo install --git https://github.com/ShadowsKeep/amp

How it works

From zero to shared AI tooling in three commands

No more copy-pasting MCP JSON into every client's config file. AMP owns the writes.

Initialize a project

Creates amp.json, a lockfile, and an ai_modules/ cache dir.

amp init

Add a skill

AMP prompts for permissions, resolves the package, then writes native config files into your repo.

amp add filesystem

Open any AI client

Claude Code, Cursor, VS Code — every detected client picks up the tool automatically. No restart of AMP required.

claude .

Architecture

One source of truth.
Many targets.

AMP keeps a single manifest (amp.json) and fans out to the native config file each AI client expects. Writes are atomic — existing files are backed up to .bak before any change.

Local scope writes per-project files. Commit them — teammates just open the repo.
Global scope (-g) injects into each client's system-wide config.
Lockfile (amp.lock) pins versions and integrity hashes.
No runtime dep on AMP — clients run MCP servers directly once config is written.

amp add filesystem

Resolves, prompts permissions, writes

Claude Code.mcp.json

Cursor.cursor/mcp.json

VS Code.vscode/mcp.json

JetBrains.junie/mcp/mcp.json

Warp.mcp.json

Claude Desktopglobal

Features

Tiny surface. Serious power.

A handful of commands that replace a spreadsheet of MCP snippets.

One command install

Add any MCP server once. AMP writes the right config for every detected AI client — automatically.

Permission-first

Before writing a byte, AMP shows which of network, fs-read, fs-write, or subprocess a tool needs.

Curated registry

25+ verified MCP servers. Custom packages too via npm:, pip:, or github: prefixes.

Bridge mode

Expose installed MCP tools as an OpenAI-compatible API on localhost:1337. Plug any OpenAI SDK straight in.

Project & global scopes

Commit amp.json for per-repo tools. Or -g to inject globally into every AI client. Lockfile keeps it reproducible.

Doctor command

Run amp doctor to verify runtimes (Node, npx, uv, uvx), detect AI clients, and diagnose project state.

Config

Reproducible by design.

amp.json is your manifest. It lists dependencies and the permissions each one has been granted. Commit it. Teammates run amp install and get the exact same setup.

Paired with amp.lock, which pins resolved versions and integrity hashes, you get the npm experience for AI skills.

See all commands

amp.json

{
  "name": "my-project",
  "version": "1.0.0",
  "dependencies": {
    "filesystem": "latest",
    "github":     "latest",
    "postgres":   "latest"
  },
  "permissions": {
    "filesystem": ["subprocess", "fs-read"],
    "github":     ["subprocess", "network"],
    "postgres":   ["subprocess", "network"]
  }
}

Registry

25+ curated MCP servers

Verified and ready. Or bring your own with npm:, pip:, github:.

filesystem

npx

Read/write local files

github

npx

Repos, issues, PRs, code search

gitlab

npx

GitLab repos, issues, MRs

postgres

npx

PostgreSQL queries

memory

npx

Persistent knowledge graph memory

sequential-thinking

npx

Dynamic reasoning tool

brave-search

npx

Brave web searchAPI key

slack

npx

Slack messages & channelsbot token

puppeteer

npx

Headless browser automation

playwright

npx

Multi-browser automation

mongodb

npx

MongoDB queries

exa

npx

Exa AI-powered searchAPI key

tavily

npx

Tavily search for agentsAPI key

perplexity

npx

Perplexity AI searchAPI key

cloudflare

npx

Workers, KV, D1, R2

stripe

npx

Payments, customers, subscriptionsAPI key

sentry

npx

Error tracking and issues

notion

npx

Pages, databases, blocksintegration token

figma

npx

File data & component inspectionAPI key

sqlite

uvx

SQLite queries

fetch

uvx

Fetch web pages as markdown

git

uvx

Git history, diffs, commits

mysql

uvx

MySQL queries

redis

uvx

Redis key-value access

aws-docs

uvx

AWS service documentation search

aws-cdk

uvx

AWS CDK guidance

Reference

Commands at a glance

A tiny surface area. Works the way npm does — but for AI tooling.

Command	What it does
`amp init`	Create `amp.json` and `ai_modules/` in the current directory.
`amp add <pkg>`	Add a local package — writes per-project config files for every detected client.
`amp add -g <pkg>`	Add a global package — injects into all AI client configs system-wide.
`amp remove <pkg>`	Remove a local package. `-g` removes globally.
`amp install`	Re-sync all packages from `amp.json`. `-g` syncs the global file.
`amp list`	Show installed packages and per-project config file status.
`amp search [q]`	Browse available packages in the registry.
`amp doctor`	Check runtimes, AI clients, and project status.
`amp bridge`	Start a local OpenAI-compatible proxy on `localhost:1337`.

FAQ

Questions, answered.

How is this different from editing .mcp.json by hand?

Every client has its own config file path, its own format for the same MCP server, and its own assumptions about env vars and binary paths. AMP knows all of them. You write amp add github once; it fans out to .mcp.json, .cursor/mcp.json, .vscode/mcp.json, and .junie/mcp/mcp.json — atomically, with a .bak of whatever was there before.

Is AMP running in the background?

No. AMP is a one-shot CLI. It writes native config files your AI clients already read. Once amp add finishes, AMP is out of the loop — the clients run the MCP servers directly. Bridge mode is the one exception: amp bridge runs a local server while you want it to.

Do I need Rust to install?

No. The install scripts fetch a pre-built binary for your platform from GitHub Releases. If you want to build from source, cargo install --git https://github.com/ShadowsKeep/amp works with Rust 1.80+.

What runtimes do I need for the packages themselves?

AMP writes config; the AI client runs the package. Node packages need npx (install Node.js). Python packages need uvx (install uv). Run amp doctor to check what's on your system.

What about secrets like API keys?

Packages that need credentials (Brave, Stripe, Notion, etc.) prompt during amp add. Values are written into the client config files, not into amp.json — so your manifest stays safe to commit. For teammates, re-run amp add locally with your own key.

Can I use AMP with a package that isn't in the registry?

Yes — use a prefix: amp add npm:@my-org/mcp-server, amp add pip:my-mcp-tool, or amp add github:org/repo. AMP resolves the runtime and writes config the same way it does for registry packages.

Install AI skills once.
Available everywhere.

From zero to shared AI tooling in three commands

Initialize a project

Add a skill

Open any AI client

One source of truth.
Many targets.

Tiny surface. Serious power.

One command install

Permission-first

Curated registry

Bridge mode

Project & global scopes

Doctor command

Reproducible by design.

25+ curated MCP servers

Commands at a glance

Permission-first by default.

Questions, answered.

Stop copy-pasting MCP JSON.

Install AI skills once.Available everywhere.

From zero to shared AI tooling in three commands

Initialize a project

Add a skill

Open any AI client

One source of truth.Many targets.

Tiny surface. Serious power.

One command install

Permission-first

Curated registry

Bridge mode

Project & global scopes

Doctor command

Reproducible by design.

25+ curated MCP servers

Commands at a glance

Permission-first by default.

Questions, answered.

Stop copy-pasting MCP JSON.

Install AI skills once.
Available everywhere.

One source of truth.
Many targets.