Skip to main content
Piloterr
ChatGPT logo

MCP & IDE agents

Use Piloterr in ChatGPT Developer mode

ChatGPT does not read .mcp.json or config.toml. In Developer mode you create a remote MCP connector: streaming HTTP, base URL https://mcp.piloterr.com/, API key as required in OpenAI’s settings.

  • Remote connector in ChatGPT settings, no local config file
  • Developer mode only, not a custom GPT action and not Codex TOML
  • Conversation-first: research and extract without an IDE
  • Same hosted library and x-api-key credits as every other MCP client

At a glance

Remote

MCP connector

SSE

streaming HTTP

190+

library tools

Chat

no IDE required

Why connect ChatGPT

  • There is nothing to commit

    Unlike Cursor or Codex, ChatGPT stores the connector in your OpenAI account. Teammates add their own connector and key.

  • Developer mode is the switch

    Without Developer mode, ChatGPT will not offer a remote MCP connector. Enable it in OpenAI developer settings, then add the server.

  • Not a browsing tab of mcp.piloterr.com

    If you open the URL in Safari you will not see tools. ChatGPT’s connector sends MCP Accept headers. The browser does not.

  • Different from Codex

    Codex is a coding agent with ~/.codex/config.toml. This page is ChatGPT chat. Same Piloterr host, different product.

What ChatGPT is good at with Piloterr

Conversational research, not repo edits.

  • Briefings without an editor

    A PM or analyst can ask for company, SERP, or marketplace JSON without installing Cursor.

  • One-off URL inspection

    Paste a URL, ask ChatGPT to crawl or render through Piloterr, and discuss the fields in the same thread.

  • No shared .mcp.json

    Do not tell ChatGPT users to “add JSON to the repo.” Send them this page and the dashboard key flow.

  • Credits still apply

    Every tool call bills the Piloterr key you attached. Say so in the thread if someone else will reuse the chat.

ChatGPT connector vs IDE MCP

ApproachDIYPiloterr
Config fileCursor .mcp.json / Codex TOMLOpenAI account connector
Who it is forDevelopers in a repoAnyone in a ChatGPT thread
Writes your codeIDE agents doChatGPT explains, you paste
Custom GPT actionsYou wrap REST yourselfHosted MCP tools already exist

Add the connector in ChatGPT

  1. Step 1

    Create an API key

    In the Piloterr dashboard. You will paste it where OpenAI asks for the connector secret.

    Create an API key
  2. Step 2

    Turn on Developer mode

    Follow OpenAI’s Developer mode guide. The remote MCP UI is not on the default ChatGPT settings screen.

  3. Step 3

    Create a remote MCP connector

    Base URL https://mcp.piloterr.com/. Transport: streaming HTTP / SSE. Attach x-api-key as the docs for that screen require.

  4. Step 4

    Start a chat and call a tool

    Ask for a crawl or a library lookup. If ChatGPT cannot see tools, re-open Developer mode and confirm the connector is enabled for that chat.

Workflow recipes

  • Competitive snapshot in a standup

    Ask ChatGPT to crawl two pricing URLs and summarize plan names, no IDE open.

  • Lead research in a shared thread

    Company plus email tools, then a paragraph you paste into the CRM.

  • Marketplace listing QA

    Product tools for Amazon or another shop, ChatGPT flags missing fields in the copy.

  • Explain a blocked page to a non-dev

    WebUnlocker or render, then a plain-language note you can send to support.

ChatGPT vs other Piloterr MCP clients

  • Scenario

    You work in ChatGPT, not an IDE

    Recommendation: This page, Developer mode

  • Scenario

    You want OpenAI to edit the repo

    Recommendation: Codex config.toml

  • Scenario

    You want an IDE with git

    Recommendation: Cursor MCP

  • Scenario

    You need a long-running personal agent

    Recommendation: Hermes Agent

Values to paste in the connector UI

ChatGPT has no project file. This JSON is only a checklist for the form, not something you commit.

JSON
{
  "name": "piloterr",
  "mcpBaseUrl": "https://mcp.piloterr.com/",
  "transport": "streaming-http",
  "headers": {
    "x-api-key": "your-x-api-key"
  }
}

Transparent credit pricing

Pay only for successful requests. Start with +500 credits, then scale with plans from $49/mo.

Premium

$49/mo

18,000 credits

Premium+

$99/mo

40,000 credits

Startup

$249/mo

110,000 credits

Ready to get started?

Your web scraping API is one click away. Start with +500 credits, no infrastructure to set up, no proxies to manage, and no credit card required.

  • +500 credits
  • No credit card required
  • All endpoints included