Copy page

MCP

Shape a project with MCP

Shaping is everything before a deploy: making the project folder, choosing the services, and setting the portal's name, the API, the docs pages and the plans. It only changes files in the folder; nothing reaches the platform yet.

Start a project

A new project with every service and a sample backend, ready to deploy:

Create an APItoGo project called Books in ./books.

The agent calls apitogo_create with template: "full". For empty services it uses template: "blank", and services picks only some of them:

Service	What it is
portal	The developer website: landing page, docs, API reference
gateway	API protection: keys, rate limits, quotas
identity	Login for the people who use your API
plans	Pricing and API keys

An existing API repository? The agent calls apitogo_init in that folder, then apitogo_add for each service, for example a gateway in front of an API that already runs:

Code
{
  "service": "gateway",
  "options": { "origin": "proxy", "url": "https://api.example.com", "spec": ["openapi.yaml"] }
}

Change it

apitogo_config makes the common changes, with the flags of apitogo config:

Change	Options
Portal name	title
Add an OpenAPI file	openapi
A docs page	pageSlug, pageTitle, pageContent (markdown)
A plan	planSku, planName, planPrice, planRate, planQuota
A contact-us plan	planSku, planPrice: "custom"
Take a plan out	removePlan
Anything else in the config	patch (an object merged into apitogo.config.json)

Example prompt:

Add a Team plan at 49 USD a month with 120 calls a minute and 200,000 calls a month.

The agent sends {"planSku":"team","planName":"Team","planPrice":"49","planRate":"120/60","planQuota":"200000/30"}.

The landing page (apitogo/portal/landing/LandingPage.tsx), the footer, the theme and the pages are your project's files: the agent edits them directly, like any code.

Selling paid plans needs a Starter or Professional project and your Stripe keys, which you set yourself; see Plans and the Stripe guide.

Check and look

• apitogo_check finds mistakes in the config and its files before a deploy. With offline it asks the platform nothing.
• To see the portal locally, run apitogo run in the folder yourself; it keeps running, so it is not an MCP tool.

Next

When it looks right, go live.