MateMCP MCP server

MateMCP

Your agent hit a limit? Keep working.

Website: matemcp.com · Account portal: api.matemcp.com · Releases: agent-latest

MateMCP helps you get more useful work from the AI plan you already pay for. When a provider's built-in coding or agent tool reaches its usage limit but the AI chat itself is still available, MateMCP gives that conversation a controlled path to your own Windows or macOS computer — so useful work can keep moving on your real projects and tools.

MateMCP does not increase or bypass a provider's usage quota. It gives compatible AI clients another way to work through MCP, using your machines and your access rules.

Bring your own AI. Connect ChatGPT, Claude, Grok, or another compatible MCP client to an enrolled MateMCP Agent. The Agent can work with project files, shells, browsers, desktop applications, attachments, secrets, and durable project context while MateMCP keeps access scoped, authenticated, observable, and approval-aware.

The public website at matemcp.com is the product and onboarding surface. The authenticated account portal at api.matemcp.com handles account access, enrolled devices, approvals, and administration. The normal desktop experience remains simple: install MateMCP Desktop, enroll the device, copy its MCP URL into your AI client, and authorize it with OAuth. You do not copy Agent credentials or expose local ports to the Internet.

Why MateMCP?

• Keep going when built-in agents stop — if the chat is still available, give it a controlled path to your own tools instead of ending the work session.
• Make more of the AI plan you already have — use capable chat time for real local work without requiring MateMCP to replace your AI provider.
• Bring your own AI — use ChatGPT, Claude, Grok, or another compatible MCP client with the same local Agent model.
• Work on real machines — files, shells, browsers, desktop apps, attachments, and project context live where your work already lives.
• Stay in control — project scopes, OAuth, approvals, auditability, and local secret handling keep powerful access explicit.

What can MateMCP do?

• Project-scoped filesystem access — read and modify files only inside configured projects.
• Shell and interactive terminal sessions — run commands, keep long-lived shells, resume output after transient reconnects, and inject approved secrets without revealing them to the AI.
• Computer Use — inspect screenshots, interact with browser/native UI, click, type, scroll, and use semantic accessibility actions where supported.
• Browser automation and visual QA — navigate applications, inspect responsive layouts, capture screenshots, and support frontend/desktop verification workflows.
• Secure attachment transfer — upload conversation files to a selected Agent using bounded, resumable, integrity-checked transfers.
• Approvals — require local or remote approval for sensitive actions and keep decisions auditable.
• Secret Manager — keep user-managed credentials in the operating system credential store instead of model context or project files.
• Activity, audit, and diagnostics — see what the Agent is doing, inspect approval/credential activity, and diagnose connectivity or execution failures.
• Skills & Memory — keep global cross-project knowledge in the Agent, while project-specific knowledge lives as versioned repository SKILL.md files and travels with Git.
• Multi-device access — enroll multiple independently revocable Agents under one account.
• Resilient connectivity — logical sessions survive short Agent/Relay disconnects, operations use stable identities, and supported streams/transfers can resume safely.

How it fits together

Shortened. The full README is on GitHub.