For AI · Model Context Protocol
Use Afore inside Claude, ChatGPT, Cursor & more.
One URL. No install. Le Journal's editorial and The Library's destination guides — luxury travel for the Côte d'Azur, Provence, and Mediterranean Europe — available in any AI chat that speaks the Model Context Protocol.
MCP server URL
https://www.afo.re/api/mcp
Streamable HTTP · stateless · public · read-only
10 tools
Search, read full articles, and pull structured place datasets — no scraping.
2 living catalogs
Le Journal editorial and The Library guides, refreshed hourly from the same CMS.
Public · read-only
No API key, no OAuth, no install. One optional token unlocks paid guide bodies.
Add to Claude.ai
Custom connectors are available on Claude.ai (web) for Pro, Max, Team, and Enterprise plans.
- Open claude.ai and go to Settings → Connectors.
- Click Add custom connector.
- Name it
Aforeand paste the URLhttps://www.afo.re/api/mcp. - Leave the OAuth Client ID and Secret blank — Afore is public and read-only.
- Click Add, then toggle Afore on in the per-chat tools menu.
Add to ChatGPT
Available in the ChatGPT desktop app and recent web builds for Plus, Pro, Team, and Enterprise plans. The connector menu may be labeled "Connectors" or "MCP servers."
- Open ChatGPT → Settings → Connectors (enable Developer mode if you don't see it).
- Click Add custom connector / Add HTTP server.
- Name it
Afore, pastehttps://www.afo.re/api/mcp, and save. - Authentication: None.
Add to Cursor
Cursor → Settings → MCP & Integrations → Add new MCP server, choose URL / HTTP, and paste the URL. Or drop this straight into .cursor/mcp.json:
{
"mcpServers": {
"afore": {
"url": "https://www.afo.re/api/mcp"
}
}
}Try it first: Inspector & curl
Poke at the server before wiring it into a client.
MCP Inspector (visual)
npx @modelcontextprotocol/inspector
# then paste https://www.afo.re/api/mcp into the URL fieldcurl (raw JSON-RPC)
curl -X POST https://www.afo.re/api/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "afore_search",
"arguments": { "query": "Cannes", "limit": 5 }
}
}'Legacy: SSE & local stdio
Clients that only support the older SSE transport can use https://www.afo.re/api/sse.
For clients without remote MCP support, a local stdio server that calls Afore's public APIs lives in mcp/afore-server of the repo — build it, then point your client at the compiled entry:
{
"mcpServers": {
"afore": {
"command": "node",
"args": ["/absolute/path/to/afore/mcp/afore-server/dist/index.js"],
"env": { "AFORE_API_BASE": "https://afo.re" }
}
}
}What can I ask?
Just chat. The assistant picks the right tool.
Discover
- “Search Afore for Côte d'Azur hotels.”
- “What has Le Journal written about Cannes?”
- “List every guide in The Library.”
Read the writing
- “Read the full Cannes Film Festival article from Le Journal.”
- “What's inside the Cannes Film Locations guide?”
- “Summarize Afore's latest editorial, with the author and canonical link.”
Places & maps
- “Show me the Cannes film locations with GPS coordinates.”
- “Which hotels has Afore covered in Provence?”
- “Give me drive times between the Cannes filming locations.”
Plan a trip
- “Plan a film-lover's week on the Côte d'Azur using Afore's guides.”
- “Recommend Afore articles for a first trip to the French Riviera.”
- “Build a Mediterranean itinerary and cite the Afore sources.”
Tip: if the assistant doesn't reach for the connector, prefix your question with “using Afore, …” and it'll call a tool instead of guessing from training data.
Tools exposed
Ten tools the assistant can call.
afore_searchFull-text search across journal articles and library guides. Ranks by destination, hotel mentions, category, and excerpt.
afore_list_journalCatalog of every Le Journal article — title, slug, excerpt, author, publish date, destinations.
afore_list_libraryCatalog of every Library guide — title, tagline, what's inside, who it's for, free vs. paid.
afore_get_articleFull Markdown text of a single journal article, with YAML front-matter and canonical URL.
afore_get_guide_metadataPublic metadata for a single Library guide. The paid editorial body is never returned.
afore_list_placesEvery named place Afore has covered — Library locations (with GPS and film cross-references) plus Le Journal destinations and hotel mentions. Optional destination and kind filters.
afore_cannes_placesStructured dataset for the Cannes Film Locations guide — 34 locations, GPS coordinates, drive times, and the films that touched each one.
afore_journal_rssRSS 2.0 feed of Le Journal.
afore_llms_txtThe site's llms.txt — content policy, citation guidance, and an index of machine-readable resources.
afore_get_full_guideTokenFull editorial body of a paid guide. Requires an Insider bearer token. Free sample guides need no token.
No MCP? Read us as JSON, RSS, or Markdown.
The same content, plain HTTP.
- /.well-known/mcp.json
MCP service descriptor
Auto-discovery for MCP-aware clients.
- /.well-known/ai-catalog.json
ARD agentic resource catalog
Agentic Resource Discovery manifest — MCP, OpenAPI, places, RSS, image sitemap, registry, and per-guide datasets.
- /api/a2a
A2A Answer Engine
Travel planning Q&A agent — POST { query } for cited Le Journal and Library matches. Agent card at /.well-known/agent-card.json.
- /agents.json
agents.json discovery manifest
MCP, ARD catalog, OpenAPI, llms.txt, and partner docs for agent platforms.
- /openapi/afore-public-api.yaml
OpenAPI 3.1 specification
Machine-readable schema for every public REST endpoint.
- /llms.txt
llms.txt
Site summary, policies, and a curated index of resources.
- /api/public/v1/journal
Le Journal — JSON catalog
Every article — title, slug, excerpt, author, publish date.
- /api/public/v1/library
The Library — JSON catalog
Every guide — public metadata only. Paid bodies are never exposed.
- /api/public/v1/places
Global places catalog
Every named place across all Library guides and Le Journal. Supports ?destination and ?kind filters.
- /journal/cannes-film-festival.md
Markdown views
Append .md to any article or guide URL for clean Markdown with YAML front-matter.
For partners
Need full guide access for an integration?
The read tools are open to everyone. Travel platforms, hotel partners, and AI products that want the full editorial body of a paid guide can request an Insider bearer token for afore_get_full_guide. We'll review the use case and either issue a token or work with you on a tailored licensing arrangement. See also Afore for partners.
Troubleshooting
If something won't connect.
The client says “Couldn’t reach the MCP server.”
Use the exact URL https://www.afo.re/api/mcp with no trailing slash. Important: use the www host — the bare afo.re/api/mcp issues a redirect that some MCP clients won’t follow on a POST. If the error persists, remove and re-add the connector; clients often cache the failure state.
The assistant answers from training data instead of Afore.
Make sure the connector is toggled on for the conversation. Prefixing your prompt with “using Afore…” nudges the model to call a tool instead of guessing.
afore_get_full_guide says access denied.
Paid Library guide bodies require an Insider token. Use afore_get_guide_metadata for the public summary, or email info@afo.re to request a token. Free sample guides need no token.
Is there an authentication option?
The read tools are intentionally public and read-only. The only credential is an optional Insider bearer token for reading paid guide bodies via afore_get_full_guide.
Building something with Afore?
Afore is written by people. Read us through whatever assistant you like — the trips are still planned by humans.
Florence · Paris · Côte d'Azur · Kennebunk
Meet the team




