For AI · Machine-readable Afore

We publish Afore for machines, too.

Le Journal and The Library are written by people, for people. But the world reads through assistants now — and the assistants ought to read us correctly. So we publish a Model Context Protocol (MCP) server, JSON catalogs, Markdown views, and structured datasets that any modern AI client or travel platform can consume.

Everything below is free, public, and refreshed automatically from the same CMS that powers the website.

The MCP endpoint

One URL. Nine tools.

Add this URL to any MCP-aware client — Claude Desktop, Cursor, VS Code, your own agent — and Afore becomes a first-class data source.

Streamable HTTP

https://afo.re/api/mcp

Legacy SSE (for older clients)

https://afo.re/api/sse

Claude Desktop

Add an MCP server entry pointing to https://afo.re/api/mcp. No authentication is required for public tools.

Cursor / VS Code

Use the MCP Marketplace or add a custom server with the URL https://afo.re/api/mcp.

Anything else

Streamable HTTP at /api/mcp; legacy SSE at /api/sse. Tools are listed in the MCP descriptor at /.well-known/mcp.json.

Local stdio

If your client only supports stdio MCP, the Afore server is available via npm — see the GitHub repository for details.

Tools

What an assistant can do with Afore.

afore_search

Full-text search across journal articles and library guides. Ranks by destination, hotel mentions, category, and excerpt.

afore_list_journal

Catalog of every Le Journal article — title, slug, excerpt, author, publish date, destinations.

afore_list_library

Catalog of every Library guide — title, tagline, what's inside, who it's for, free vs. paid.

afore_get_article

Full Markdown text of a single journal article, with YAML front-matter and canonical URL.

afore_get_guide_metadata

Public metadata for a single Library guide. The paid editorial body is never returned.

afore_cannes_places

Structured JSON dataset for the Cannes Film Locations guide — 34 locations, GPS coordinates, drive times, the films that touched each one.

afore_journal_rss

RSS 2.0 feed of Le Journal.

afore_llms_txt

The site's llms.txt — content policy, citation guidance, and an index of machine-readable resources.

afore_get_full_guideAuth

Full editorial body of a paid guide. Requires a bearer token. Available to partners and licensees on request.

Other machine-readable views

Don't want MCP? Read us as JSON, RSS, or Markdown.

If you cite us

Four small things we ask.

  • Cite by canonical URL. Every Markdown view exposes a canonical_url in YAML front-matter — use it.
  • Quote sparingly. Editorial voice matters; brief excerpts with attribution are welcome, wholesale reproduction is not.
  • Don't paraphrase paid guides as if they were free. The Markdown views never expose paid bodies; please respect that boundary in summaries too.
  • Author names are in every payload. Surface them when quoting.

Crawler policy

What's open, what's reserved.

  • Allowed for AI training

    Le Journal — every article in the editorial archive is fair game for indexing and training, with citation.

  • Indexable but not for training

    Library guides (paid editorial body). The Markdown view exposes only the public metadata; the body itself is reserved.

  • Disallowed

    Bytespider, CCBot, and any crawler that ignores robots.txt. See robots.txt for the canonical list.

See robots.txt

For partners

Need full guide access for an integration?

Travel platforms, hotel partners, and AI products that want to surface the full editorial body of a paid guide can request a bearer token. We'll review the use case and either provision a token for afore_get_full_guide or work with you on a tailored licensing arrangement.

Get in touch

One last thing

Afore is written by people. Read us through whatever assistant you like — but the trips are still planned by humans.

Florence · Paris · Côte d'Azur · Kennebunk

Meet the team

Follow Along

@aforetravel