Frisky Dev Cloud

MCP Integration Hub

One accelerated builder ecosystem for turning ideas into running Frisky tools: MCP clients, GPT Actions, REST automations, Codex configs, Telegram, and agent runners.

integrations.json openapi.json codex.mcp.json cli.json CLI script specialists.json

MCP Clients

Codex, Cursor, Antigravity, and ChatGPT all point at the same remote MCP endpoint.

Endpoint

Remote MCP surface

Use this for ChatGPT Developer Mode, MCP-aware agents, and tool clients that support streamable HTTP.

https://mcp.friskydev.com/mcp

Codex

MCP server JSON

Install the repo plugin at plugins/frisky-dev-mcp, or copy this config into MCP-capable clients that accept remote server URLs.

{
  "mcpServers": {
    "frisky-dev-mcp": {
      "type": "http",
      "url": "https://mcp.friskydev.com/mcp"
    }
  }
}

Cursor

Cursor MCP config

Use the same remote MCP bridge for coding sessions, reviews, and specialist planning inside Cursor.

https://mcp.friskydev.com/cursor.mcp.json

Antigravity

Antigravity MCP config

Use Frisky MCP as the Antigravity cloud tool surface for product, infrastructure, launch, and execution routing.

https://mcp.friskydev.com/antigravity.mcp.json

Actions + REST

GPTs, bots, and services can call the same specialist action without embedding secrets in prompts.

GPT Actions

OpenAPI import

Import this schema in GPT Builder. Configure API Key authentication as Bearer using your Frisky bot token.

https://mcp.friskydev.com/openapi.json

REST tools

Consult specialist

Use a Frisky OAuth access token from the MCP login flow for human/interactive calls, or a machine bearer token for server jobs.

POST https://mcp.friskydev.com/consult_specialist
Authorization: Bearer $FRISKY_ACCESS_TOKEN_OR_BOT_TOKEN
Content-Type: application/json

{
  "slug": "frisky-director",
  "request": "Prioritize today's beta work.",
  "live_call": true
}

CLI

A tiny shell runner for local machines, CI, Coolify dev containers, and ops scripts.

Install

Terminal support

Download the CLI, inspect it, then run text-first packet or live consult commands.

curl -fsS https://mcp.friskydev.com/frisky-mcp-cli.sh -o frisky-mcp
chmod +x frisky-mcp
./frisky-mcp specialists

Examples

Packet and live call

Packet mode needs no machine token. Live consults use a Frisky OAuth access token or server bot token.

./frisky-mcp packet frisky-codex-engineer "Review deployment risk"

FRISKY_ACCESS_TOKEN=... ./frisky-mcp consult frisky-director "Prioritize beta work"
FRISKY_BOT_API_TOKEN=... ./frisky-mcp consult frisky-director "Prioritize beta work"

Backend Integrations

Database and edge runtimes call specialists from server-side code only.

Neon

Database agents

Neon-backed agents can call Frisky Data Model, SaaS Infrastructure, or Codex Engineer through the REST action endpoint.

POST https://mcp.friskydev.com/consult_specialist
Authorization: Bearer $FRISKY_BOT_API_TOKEN

{
  "slug": "frisky-data-model",
  "request": "Review this schema migration.",
  "live_call": true
}

Supabase

Edge Function call

Supabase Edge Functions can call the same live specialist endpoint with bearer auth stored as a project secret.

await fetch("https://mcp.friskydev.com/consult_specialist", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${Deno.env.get("FRISKY_BOT_API_TOKEN")}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    slug: "frisky-trust-safety",
    request: "Review this auth policy.",
    live_call: true
  })
})

Secrets + Dev Runtime

Infisical is the vault. Coolify is the dev runtime. Browsers and GPT instructions get placeholders only.

Infisical

Vault source of truth

Store machine tokens, model keys, database credentials, and signing secrets in the vault, then sync them into server runtimes.

Infisical vault
  -> Cloud Run env
  -> Coolify dev env
  -> Frisky MCP server

Coolify

Dev runtime

Use Coolify for dev deployments that need the same machine token contract as production without exposing secrets client-side.

Machine/server auth:
FRISKY_BOT_API_TOKEN

Human/interactive auth:
Frisky OAuth access token from MCP login

Security rule: never place service-role keys, database credentials, model API keys, or machine tokens in browser clients, public MCP configs, GPT instructions, or screenshots. Use bearer placeholders in docs and inject real secrets server-side only.