Bring Your AI Mcp Config Migration.json API
The Mcp Config Migration.json API from Bring Your AI — 1 operation(s) for mcp config migration.json.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bringyour-ai:bringyour-ai-mcp-config-migration-json-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Bring Your AI Mcp Config Migration.json API
description: 'Public surface for Bring Your AI — the local-first AI agent harness migration,
central Claude/Codex/Cursor sync, sanitized distill snapshot, and no-data
remote MCP server.
The primary programmable surface is the Model Context Protocol endpoint at
`/mcp` (streamable-http JSON-RPC 2.0). REST endpoints below are for discovery
and billing. The MCP discovery manifest is available at
`/.well-known/mcp.json`.
Remote MCP is no-data. It exposes discovery, preview, target listing, and
local install handoff only. It does not accept harness files, generated
memories, user rules, API keys, GitHub handles, or file contents. Actual
moves, central sync, distill snapshots, and first-setup builds run through
the local CLI or local MCP server on the user''s machine. Central sync uses
a local hub by default, can use a user-selected Git repo path, keeps auto
sync disabled by default, never performs Git remote actions, and leaves
platform-native config target-local by default during cross-tool sync.
Commerce endpoints expose a machine-readable catalog, quote, and checkout.
The $499 Team Migration Pack includes one guided migration and onboarding
for up to 10 people, plus 10 lifetime licenses. It uses a dynamic Stripe
Checkout Session. Existing individual licenses keep their Payment Links.
Stripe shared payment token
settlement is live for agents: submit a Link-issued token and buyer email to
create a server-confirmed PaymentIntent and receive the signed license in JSON.
x402/MPP is reserved for future per-call API endpoints.'
version: 1.2.0
contact:
email: hello@bringyour.ai
license:
name: Proprietary — from $19 lifetime license
url: https://bringyour.ai/buy
servers:
- url: https://bringyour.ai
description: Production
tags:
- name: Mcp Config Migration.json
paths:
/mcp-config-migration.json:
get:
summary: Agent-readable MCP config migration checklist
description: 'Structured checklist for agents validating MCP config during a Claude
Code to Codex migration. The route is descriptive only and preserves
the no-data remote invariant: it does not accept or process MCP config
files, generated memories, user rules, API keys, GitHub handles, local
paths, or file contents.'
operationId: mcpConfigMigrationChecklist
responses:
'200':
description: MCP config migration checklist
content:
application/json:
schema:
type: object
tags:
- Mcp Config Migration.json