Allows Perplexity to add Journey AI as a remote MCP connector and access Journey Foods supplier, ingredient, commodity price, lab result, and product formulation data.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Journey AI is the official Model Context Protocol (MCP) server from Journey Foods. It gives AI agents and assistants such as Claude, ChatGPT, Cursor, VS Code and Perplexity read-only access to Journey's food and CPG data: supplier search and comparison, ingredient nutrition and sustainability profiles, commodity reference prices with history and forecasts, Journey Labs verified test results, and (for signed-in customers) your own product formulations.
Hosted server: https://mcp.journeyfoods.io/mcp (Streamable HTTP)
Local package: npx -y @journeyfoods/mcp (stdio)
Docs: docs.journeyfoods.io · Website: journeyfoods.io
Every tool is read-only. Journey AI never creates, changes or deletes data.
Get a free trial key at price.journeyfoods.io. Developer API keys for ingredient data are at dev.journeyfoods.io.
Related MCP server: a2a-grocery
You can use the hosted server (nothing to install) or run the package locally with npx. Ready-made configs are in examples/.
Hosted: Settings → Connectors → Add custom connector. Use the URL https://mcp.journeyfoods.io/mcp and send your key in the x-api-key header.
Local (Claude Desktop): add examples/claude-desktop.json to claude_desktop_config.json, then restart Claude. That block sets JOURNEY_PRICE_API_KEY (price tools; base https://price.journeyfoods.io). Add JOURNEY_API_KEY from dev.journeyfoods.io in the same env object for ingredient tools (base https://devapi.journeyfoods.io). Supplier tools use the hosted server unless you set JOURNEY_SUPPLIER_API_BASE_URL.
claude mcp add --transport http journey https://mcp.journeyfoods.io/mcp --header "x-api-key: YOUR_JOURNEY_API_KEY"ChatGPT connectors need OAuth sign-in, which is coming soon on the hosted server, along with a ChatGPT directory listing. Until then, use Journey AI from any of the clients below.
Add examples/cursor-mcp.json to .cursor/mcp.json (hosted). For local use, use the npx block from the Claude Desktop example.
Add examples/vscode-mcp.json to .vscode/mcp.json. VS Code asks for your key and keeps it out of the file.
Plugins → Add custom → Connector → Add MCP connector → Remote. Use the URL https://mcp.journeyfoods.io/mcp, choose API key authentication, and paste your key.
Point any client that supports Streamable HTTP at https://mcp.journeyfoods.io/mcp with the x-api-key header (see examples/remote-generic.json). For stdio clients, run npx -y @journeyfoods/mcp with JOURNEY_PRICE_API_KEY set. Add JOURNEY_API_KEY for ingredient tools. Those are different keys.
# Price tools. Base defaults to https://price.journeyfoods.io
JOURNEY_PRICE_API_KEY=... npx -y @journeyfoods/mcp --http # serves http://127.0.0.1:3000/mcp
# Ingredient tools also need a developer API key. Base defaults to https://devapi.journeyfoods.io
# The price feed key is not sent to the developer API.
JOURNEY_PRICE_API_KEY=... JOURNEY_API_KEY=... npx -y @journeyfoods/mcp
npx -y @journeyfoods/mcp --helpJOURNEY_API_BASE_URL overrides https://devapi.journeyfoods.io (ingredients, x-api-key). JOURNEY_PRICE_API_BASE_URL overrides https://price.journeyfoods.io (/api/v1/commodities). Supplier profiles are only on an internal backend that needs a service key. Local npx does not default a supplier URL and does not send your API key there. Unless you set JOURNEY_SUPPLIER_API_BASE_URL, supplier tools point you at the hosted server https://mcp.journeyfoods.io/mcp.
The hosted Worker (worker/wrangler.jsonc) uses the live binding names and points them at the Cloudflare fallback for the Nov 2 2026 Atlas outage: JOURNEY_DEV_API_BASE is https://journey-fallback.journeyfoods.workers.dev/x/devapi and JOURNEY_API_BASE is https://journey-fallback.journeyfoods.workers.dev/x/mcp. The file keeps the live Durable Object, KV, Analytics Engine, and secrets-store bindings. Price results from this server are indexes (base 100) and forecast ranges only.
Tool | What it does |
| Find food and CPG suppliers by name, ingredient, category, region or certification |
| Full supplier profile: website, country, locations, categories, certifications, verification status |
| Compare two to five suppliers side by side, including what they share |
| Search the Journey ingredient database, with nutrition and sustainability scores |
| Ingredient profile: nutrition per 100 g, scores, nutrients, allergens and attributes |
| Price index (base 100) and recent index history, plus an optional P10/P50/P90 forecast range. Raw prices are not returned |
| Every ingredient and commodity Journey publishes an index for (names and units only; no levels) |
| Search your own products and formulations (signed-in Journey accounts) |
| One of your products: summary, ingredients and nutrition panel |
| Check whether an ingredient, product or supplier has a Journey Labs verified result |
If a data source needs something this process does not have, the tool says what to set. Ingredient tools without JOURNEY_API_KEY link to dev.journeyfoods.io. Price tools without JOURNEY_PRICE_API_KEY link to price.journeyfoods.io. Supplier tools without a supplier API base point at https://mcp.journeyfoods.io/mcp. Product tools need a signed-in Journey app account.
Plan | What you can see | Requests |
Free (Explore) | 200 products, 200 ingredients, 10 suppliers and 25 lab results per company or account (distinct records, lifetime), each under 2% | 10 per minute |
Fresh | 2% of each data type. The supplier network is not included | 60 per minute |
Supplier, Growth, Group, Startup | 2% of each data type (suppliers, ingredients, products, lab results) | 60 per minute |
Enterprise | Uncapped while the subscription is active or trialing | 300 per minute |
When you reach a limit, the tool tells you and links to upgrade options. For full data access, contact Journey about a contract.
See .env.example. Keys come from the environment, and no keys are stored in code. Each key is only sent to the service that issued it. The developer API defaults to https://devapi.journeyfoods.io (x-api-key). The price feed defaults to https://price.journeyfoods.io (/api/v1/commodities). Supplier data has no default URL. The policy file format is shown in policy.example.json.
npm install
npm test # tests use mock data only, no network
npm run buildSee CONTRIBUTING.md and SECURITY.md.
Push a v* tag, such as v0.2.1, to publish that commit. .github/workflows/publish.yml runs on GitHub Actions with Node 22:
npm ci && npm test && npm publish --provenance --access publicThe workflow uses npm Trusted Publishing (permissions: id-token: write). It does not use an NPM_TOKEN. Before the first tag, add this repository and publish.yml as a trusted publisher for @journeyfoods/mcp on npmjs.com. Tag the commit whose package.json version you want to ship (v0.2.1 publishes 0.2.1). prepublishOnly builds the package and runs the tests again before upload.
MIT © Journey Foods
mcp-name: io.journeyfoods/journey-ai
This server cannot be deployed
Find governed AI capabilities and verify signed receipts. Read-only, no account.
Free read-only lookups of Oregon contractor licenses and FDA food recalls for AI agents. No key.
Read-only access to your VortexIQ store data: audits, KPIs, alerts, Brand DNA, reports, Ask VIQ.
Read-only lookups of public AI agent pricing, free plans and source links. No API key.
