free beta · open signup

Your context.
Out of their repo.

mcpcall keeps the AI tooling you have spent years refining out of the client repos you push to. Author it once on the platform, pull it into any local checkout over MCP, and leave nothing behind when the engagement ends.

Get started View docs

.mcp.json

{
  "mcpServers": {
    "mcpcall": {
      "command": "npx",
      "args": ["-y", "@asad120414/mcpcall"],
      "env": {
        "MCPCALL_API_KEY": "${MCPCALL_API_KEY}"
      }
    }
  }
}

$ pull_workspace acme-corp

The problem

A shared .gitignore is not a security boundary.

You consult. You do not own the remote. Years of subagents, skills, and per-client conventions live on your machine — and the standard workaround for keeping them there is to copy markdown into the project and add the names to .gitignore.

That file is tracked. One git add -A away from leaking. The file names alone tell the client what you brought. And when the engagement ends there is no clean off-boarding.

mcpcall replaces the workaround with infrastructure. The files live on the platform. They land on your disk only when you ask for them, hidden from git through .git/info/exclude — user-local, never tracked, never pushed. Cleanup removes every byte.

How it works

Four commands, end to end.

01
Author on the platform
Write CLAUDE.md, subagents, skills, and slash commands in a workspace per client or project.
02
Wire up the MCP
Drop a small .mcp.json into the client repo. The mcpcall server boots via npx — no global install.
03
Pull on demand
In Claude Code, run pull_workspace <slug>. Files land in .claude/, hidden via .git/info/exclude.
04
Cleanup when done
One call. Sha-matched files removed, sentinel block stripped, repo is bit-identical to before.

MCP tools

Ten tools. One workspace per client.

Everything needed to round-trip context files between the platform and any local checkout — no clobbering, conflict-safe, fully reversible.

Read

list_workspaces: Enumerate workspaces accessible to your API key.
list_files: Manifest of files in a workspace with sha256 and size.
status: Diff local manifest against remote, per file. No writes.

Write

pull_workspace: Land files in .claude/ and add a sentinel block to .git/info/exclude. Optional prefix pulls a subtree.; pull_workspace acme-corp
pull_file: Pull a single file with the same conflict-safe, sentinel-block, manifest semantics.
create_file: Create a new file on the platform from a path or inline content.
push_file: Upsert. Reads local disk if content is omitted; new version on sha change.
import_folder: Bulk-upload a local directory tree. Glob-filtered, symlink-defended, dry-run aware.

Destructive

delete_file: Soft-delete remotely. The local copy is left alone.
cleanup: Reverse a pull. Only sha-matched files are removed; the rest are reported.

Full reference in the tool docs.

Free beta

Bring your context with you.

Open signup. Email or GitHub, your call. Free during beta — no card, no quota.

Your context.
Out of their repo.

.mcp.json

{
  "mcpServers": {
    "mcpcall": {
      "command": "npx",
      "args": ["-y", "@asad120414/mcpcall"],
      "env": {
        "MCPCALL_API_KEY": "${MCPCALL_API_KEY}"
      }
    }
  }
}

$ pull_workspace acme-corp

Your context.Out of their repo.

Four commands, end to end.

Author on the platform

Wire up the MCP

Pull on demand

Cleanup when done

Ten tools. One workspace per client.

Bring your context with you.

Your context.Out of their repo.

Four commands, end to end.

Author on the platform

Wire up the MCP

Pull on demand

Cleanup when done

Ten tools. One workspace per client.

Bring your context with you.

Your context.
Out of their repo.

Your context.
Out of their repo.