How it works

From install to live MCP server in four steps.

You don't maintain MCP code. You don't track protocol deprecations. You map endpoints; GetMCP handles the rest.

01 Install

Put it on a subdomain like mcp.mysaas.com

Upload and open it in a browser — the installer checks the server, sets up the database and creates your login. If you already run WordPress, install it there instead. Same product, same screens.

→ open mcp.mysaas.com
✓ checks · database · admin
— or — the WordPress plugin

02 Create a server

One namespace per product or tenant

Define the server URL and auth strategy. Spin up separate servers per customer or environment — your global per-client rate limit applies to each.

server  production
path    /mcp/my-mcp-server
auth    Bearer · OAuth 2.1
ready to accept tools

03 Import tools

Paste a cURL, upload an OpenAPI file

GetMCP parses your existing API definition and generates MCP tools with schemas, descriptions, and parameter validation.

import openapi.json
+ 24 tools generated
+ 3 prompts · 2 resources
review · enable · ship

04 Share the URL

Users connect from any MCP client

Ship one URL to customers. They add it to Claude, ChatGPT, VS Code, or Cursor — and your app is suddenly AI-native.

# claude_desktop_config.json
"mysaas": {
"url": "mcp.mysaas.com"
}

Where it runs

One product. Install it wherever you already are.

The standalone app and the WordPress plugin are the same codebase — same admin, same tools, same MCP endpoints. Pick whichever fits the infrastructure you already run, and move between them whenever you like.

Most people start here

Standalone app

A self-contained PHP application. Upload it, open it in a browser, and the installer takes you through requirements, database and your administrator account.

Any host with PHP 8.3+ — shared hosting, cPanel, VPS, Docker
SQLite needs no setup; MySQL and PostgreSQL supported
No WordPress, no Node, no build step
One cron line and you are done

Already on WordPress?

WordPress plugin

The same application, installed into a site you already operate — so there is no second thing to host, back up or keep patched.

Installs and updates like any other plugin
Uses WordPress logins, roles and cron
Reads WordPress posts as MCP resources
Pulls server logos from the media library

Not sure? Start on either. A server exports to a single file that recreates it — tools, resources, prompts and settings — on the other.

Import methods

Bring the API definition you already have.

Four paths in, one clean tool spec out. Or hand-author a tool when you need something bespoke.

request.sh Import source

Generated MCP tools + 1 tool

Dashboard

One pane of glass for every MCP server you run.

Server health, call volume, latency, and recent activity — all on one dashboard you host. No proxy, no third-party service, no extra account to set up.

mcp.mysaas.com/admin

Dashboard

Overview of your MCP servers and activity

6

Total Servers

47

Total Tools

12%

50

API Calls Today

218ms

Avg Response Time

MCP Server Status

5 of 6 active

View All

WordPress API

https://mcp.mysaas.com/mcp/wp-server-wp

6h agoView

Stripe API

https://mcp.mysaas.com/mcp/stripe-api

8h agoView

Notify Hub

https://mcp.mysaas.com/mcp/notify-hub

7h agoView

CRM Bridge

https://mcp.mysaas.com/mcp/crm-bridge

7h agoView

Shopify Sync

https://mcp.mysaas.com/mcp/shopify-sync

9h agoView

View all 6 servers

Quick Actions

Create Server

Set up a new MCP server

Browse Templates

Start from our built-in templates

View Docs

Learn how to use GetMCP

View Analytics

Charts, trends & performance

View Logs

Browse all API call logs

Recent Activity

last 5 API calls

View All Logs

create_invoice

stripe-api · Stripe API

SUCCESS 171 ms 3h ago

summarizeRecord

crm-bridge · CRM Bridge

SUCCESS 441 ms 3h ago

send_notification

notify-hub · Notify Hub

SUCCESS 167 ms 4h ago

search_posts

wp-server-wp · WordPress API

SUCCESS 155 ms 5h ago

Getting Started

You're all set!

Your MCP server is running and forwarding tool calls.

Tools · Prompts · Resources

Everything MCP supports. Nothing you have to build.

GetMCP mirrors the full protocol surface — tools, prompts, and resources — with a UI that makes each first-class.

T

Tools

Callable functions backed by your API. Full JSON Schema for arguments, typed responses, per-tool scopes and transforms.

tool create_invoice
args customer_id, amount, due_date
returns Invoice
scope write:billing

P

Prompts

Pre-authored prompt templates with parameters. Ship "workflows" users can invoke from their client in one tap.

prompt weekly_report
args workspace, period
template "Summarize activity in ..."
surfaced as slash-command

R

Resources

Read-only context: docs, records, live data streams. Exposed via URIs the model can pull on demand.

resource docs://api/v1
uri mcp://mysaas/docs
mime text/markdown
cached 5 min

◎

Built-in playground & logs

Test every tool with real inputs before you expose it. Inspect every call in production — request, response, latency, and the client that made it — without leaving the dashboard.

Replay any call with one click
Filter by client, tool, status, or latency
Export logs as JSON or CSV

POST /mcp/my-mcp-server/tools/call · 2026-04-24 14:22:08

{

"tool": "create_task",

"arguments": { "title": "Ship MCP" },

"client": "claude-desktop/0.8.3",

"latency_ms": 168,

"status": "ok"

}

Playground

Test every tool without leaving the dashboard.

The same request pane your users will hit through Claude or ChatGPT — but with inputs you control and responses you can inspect.

Tool

create_task

Arguments

title "Ship MCP launch page"

project_id "proj_8f21"

due_date "2026-05-02"

assignee null

200 OK · 168 ms

{

"id": "task_01HW8K3M",

"title": "Ship MCP launch page",

"project_id": "proj_8f21",

"status": "open",

"due_date": "2026-05-02",

"created_at": "2026-04-24T14:22:08Z",

"url": "https://mysaas.com/t/01HW8K3M"

}

→ 1 outbound call · 1.2 KB · no retries

Use cases

Every SaaS becomes an agent-ready SaaS.

Whether your product is a CRM, a helpdesk, or a WordPress page builder — the path is the same. Map the API, ship the server.

Project management

Let customers create tasks, reassign work, and pull sprint reports from their AI client.

list_projects create_task assign_user +9 more

Customer support

Agents triage tickets, draft replies, and close threads conversationally — grounded in your ticket data.

search_tickets reply_ticket escalate +6 more

Analytics & reporting

Expose queries and dashboards as tools. Users ask questions in plain English and get real numbers back.

run_query fetch_dashboard export_csv +4 more

E-commerce

Shoppers browse catalogs, place orders, and track shipments from within their AI assistant — no app switching.

search_products create_order track_shipment

Dev tools

Deploy, rollback, tail logs. Give AI coding assistants first-class access to your build and runtime.

deploy rollback tail_logs +5 more

Internal ops

Wire up any internal API — HR, finance, DevOps — and give your team a private AI copilot on top of it.

private sso-gated audit-logged

For developers

The protocol, abstracted. Not hidden.

GetMCP generates a compliant MCP surface from your inputs — but every tool, prompt, and resource is inspectable and editable. You stay in control; we handle the protocol churn.

Protocol updates ship as product updates — zero downtime
Per-tool scopes & OAuth 2.1, mapped to your existing auth
Versioned tool specs — deprecate safely without breaking clients
Self-hosted on your own server — your data, your domain

manifest.json generated · editable

// GetMCP auto-generates this from your API
{
  "name": "mysaas-mcp",
  "version": "1.0.0",
  "protocol": "2026-07-28",
  "transport": ["http", "sse"],
  "tools": [
    {
      "name": "create_task",
      "description": "Create a task in a project",
      "input_schema": {
        "type": "object",
        "required": ["title", "project_id"],
        "properties": {
          "title": { "type": "string" },
          "project_id": { "type": "string" },
          "due_date": { "type": "string", "format": "date" }
        }
      },
      "scope": "write:tasks"
    }
  ]
}

Pricing

Self-hosted. License-based. Yours.

A flat annual license — no per-call fees, no usage gates. Run as many servers, tools, and calls as your server can handle.

Solo

$0 / free forever

For getting your first MCP server running on any host.

1 MCP server
Up to 10 tools
1,000 calls / month
cURL import or manual tool creation
API Key, Bearer & Basic auth
Community support

Get started

Pro

$99 / year

For teams shipping a real MCP server. Unlimited everything, on one site.

Everything in Solo
Unlimited servers & tools
Unlimited calls — no metering
OpenAPI / Swagger / Postman import
Customizable analytics retention
Per-client rate limits
Priority email support
1 site

Get Pro

Agency

$299 / year

For teams managing MCP across many client sites.

Everything in Pro
Up to 25 sites
Partner support & onboarding

Get Agency

See full plan comparison →

FAQ

Questions, answered.

Where does GetMCP run?

On your own server, wherever that is. The standalone app installs on any host with PHP 8.3 and a database — shared hosting, a VPS, or Docker. You upload it, open it in a browser, and answer three screens: requirements, database, administrator. SQLite needs no setup at all, and MySQL and PostgreSQL are both supported.

If you already run WordPress, there is a plugin build that installs the same product into a site you are already operating — useful when you would rather not add another thing to maintain. Both builds share the same code: the same tools, resources, prompts, chat playground, OAuth, analytics and MCP endpoints. Neither is a cut-down version of the other.

Is the WordPress version different from the standalone app?

No. It is the same application with the same admin interface. The differences are only the ones the host forces: the standalone app has its own installer, login and cron entry, while the plugin uses WordPress's. A couple of WordPress-specific conveniences exist only in the plugin — pulling a server logo from the media library, and reading WordPress posts as a resource — because there is nothing to read from without WordPress.

You can move between them. A server exports to a single file that recreates it, with its tools, resources, prompts and settings, on the other build.

Do I need to write any MCP code?

No. You map endpoints or upload a spec, and GetMCP generates compliant tool, prompt, and resource definitions. When the MCP spec changes, an update applies the new protocol — your tools keep working.

Which MCP clients work with it?

Any client that implements MCP over HTTP or SSE. That includes Claude Desktop, Claude Code, ChatGPT, VS Code, Cursor, Zed, and a growing list of agent frameworks. Your users just paste the server URL.

How does authentication work?

Credentials are passed straight through — GetMCP never stores them. As the app developer, you share the MCP server URL and the connection method with your users. They add that URL to their MCP client (Claude Desktop, ChatGPT, VS Code, etc.) and set their own auth — typically a bearer token — in the client's header configuration.

When the client calls the server, it automatically sends those credentials along. GetMCP receives them on the request, validates them, and forwards them to your tool's underlying API. The same user identity flows end-to-end, so every call is attributed and every permission boundary your API already enforces stays in place.

Can I write tools by hand?

Yes. The manual editor lets you define tools with full JSON Schema, attach any HTTP request as the backend, and add response transformations. Handy for endpoints you don't want to expose directly.

Is my data hosted by you?

No. GetMCP runs entirely on your own server. Traffic flows from the MCP client, through your server, to your API. We never see the calls or the data.

What about analytics and logging?

Every call is recorded with tool name, client, latency, status, and payload size. Filter, replay, or export to JSON or CSV.

Install

Install in under a minute.

One command on any host with PHP 8.3 — or drop the plugin into a WordPress site you already run. No Composer, no Node, nothing to build.

Then finish in the browser: database, administrator, done. Already run WordPress? Install it there instead.

# On any host with PHP 8.3 or newer
curl -fsSL https://get.getmcp.com | bash

# In PowerShell
irm https://get.getmcp.com/install.ps1 | iex

Ship an MCP server for your app. Without writing MCP code.