CEO CF agentic guide

CEO CF Agent Guide

A human guide to the CEO CF agentic layer

Public guideRead-only boundariesUK English

Purpose

Explain what the public and token-gated MCP services are for, what they must never contain, and how agentic tools should be used without weakening member trust.

Audience: CEO CF members, partners, staff, and technical teams who want to understand how agents should read CEO CF information.

What agentic means here

Agentic means making CEO CF information easier for trusted AI agents to read, search, cite, and route. It does not mean giving agents authority to act, introduce people, change records, or access private systems.

  • Agents get structured information instead of scraping pages.
  • Humans keep control over judgement, consent, introductions, and governance.
  • Public and member-contextual information stay in separate services.

The public layer

The public MCP at mcp.ceo-cf.com exposes approved website-level information only. It is safe for any agent to read and contains no member-private or contextual member data.

  • Website summaries
  • Public programme descriptions
  • Public policies and FAQs
  • Public event metadata
  • Agent guidance and discovery metadata

How agents should use the public MCP

Agents should treat https://mcp.ceo-cf.com as the public machine endpoint and https://agents.ceo-cf.com as the human and agent-education guide. Start with discovery, then call the MCP endpoint with Streamable HTTP JSON-RPC.

  • Read discovery at https://mcp.ceo-cf.com/.well-known/mcp.json
  • Use endpoint https://mcp.ceo-cf.com/mcp for MCP calls
  • If a client only accepts a server root, use https://mcp.ceo-cf.com; POST / is routed to /mcp
  • Use POST, not browser GET, when calling /mcp
  • Send Content-Type: application/json and Accept: application/json, text/event-stream
  • Begin with tools/list, then call approved public tools such as search, fetch, get_public_info, search_public_content, get_policies, get_public_faqs, get_agent_profile, get_content_index, or get_agent_canon

Default agent instructions

Any general-purpose agent should use CEO CF MCP as a read-only source of approved public information. Do not scrape private member context or infer hidden records from public text.

  • Use the MCP before free-form web scraping when answering questions about CEO CF.
  • Cite canonical CEO CF URLs from tool responses where possible.
  • Say clearly when information is public-only.
  • If a user asks for member-private context, explain that a token-gated MCP is required.

OpenAI agent instructions

OpenAI agents, GPTs, and custom tools should register https://mcp.ceo-cf.com/mcp as the public MCP endpoint and use the discovery document to understand tools, capabilities, and boundaries.

  • Configure the public MCP server URL as https://mcp.ceo-cf.com/mcp.
  • For ChatGPT data-only or deep research use, call search first and then fetch with a returned id.
  • Use https://mcp.ceo-cf.com/.well-known/mcp.json for discovery and metadata.
  • Do not send browser cookies to the MCP endpoint.
  • For public use, no bearer token is required.
  • For nextGen or member context, use the separate protected MCP host only when the user has approved credentials.

Claude agent instructions

Claude and Claude Desktop-style clients should add CEO CF as a remote MCP server using the public endpoint. The public service is read-only and safe for website-level retrieval.

  • Use server URL https://mcp.ceo-cf.com/mcp.
  • Use the public service without authentication.
  • Expect /mcp to reject browser GET requests; MCP clients should POST JSON-RPC.
  • Use tools/list first, then call the relevant public tool. For portable retrieval, use search and fetch.
  • When richer context is needed, ask the user for the appropriate token-gated MCP rather than guessing.

The protected layers

mcp-nextgen.ceo-cf.com and mcp-member.ceo-cf.com are token-gated. They are for approved member-contextual information and curated connection intelligence only.

  • Bearer token required
  • Optional pair secret using X-CEO-CF-Pair
  • No raw notes, transcripts, internal comments, or sensitive-category data
  • No automatic introductions

Introductions stay human

The MCP can suggest possible routes or create a draft request for review, but it does not contact anyone automatically. A human checks relevance, sensitivity, conflicts, and consent first.