Fynd for AI coding agents

Connect your AI coding agent to your Fynd commerce store (catalog, orders, offers, content, and more). This repo packages portable skills plus per-platform manifests that all point at the same hosted Fynd MCP server — so the same commerce surface works across Claude Code, Codex, Copilot, and other MCP-capable agents.

What's in here

skills/                 # portable SKILL.md — Claude Code / SKILL-aware agents
.claude-plugin/         # Claude Code manifest (plugin.json + marketplace.json)
.mcp.json               # MCP connection (Claude Code reads this)
codex/                  # OpenAI Codex — config.toml block + AGENTS.md guidance
scripts/                # manifest validator

The heavy part — the commerce tools — lives in the hosted Fynd MCP server, not in this repo. Each platform just needs a thin manifest + the shared skills.

Claude Code

# Add the marketplace
/plugin marketplace add gofynd/fynd-ai-plugins
# Install the plugin
/plugin install Fynd

No URL or token to paste. The plugin's .mcp.json points at the Fynd MCP endpoint with no Authorization header, so the client self-discovers OAuth on the server's 401 challenge.

Sign in (trigger auth)

1. Restart Claude Code after installing — plugin MCP servers load at session start.
2. Run /mcp, select Fynd (it shows as "needs authentication"), choose Authenticate.
3. Your browser opens the Fynd sign-in; if you belong to more than one organization, pick one on the consent screen — the connection binds to it.

To re-authenticate or switch organizations: /mcp → Fynd → Clear authentication, then Authenticate again. There is no CLI login command in Claude Code (unlike Codex's codex mcp login fynd) — the /mcp menu is the only trigger.

The baked-in URL is the org-agnostic Fynd endpoint. Production is served under /organization/<org>/autonomous/, so the plugin uses a reserved sentinel org (_) that the server treats as org-agnostic — you pick the real org at the consent screen. For local testing, point it at http://localhost:4000/mcp/v1.

Alternative: bearer token

Prefer a token over browser sign-in? Configure the server with your org-scoped MCP URL and an Authorization header instead:

{
  "mcpServers": {
    "Fynd": {
      "type": "http",
      "url": "https://console.fynd.com/organization/<your-org>/autonomous/mcp/v1",
      "headers": { "Authorization": "Bearer <your-token>" }
    }
  }
}

The token's organization must match the one in the URL. Get the exact URL and a token from Settings → Developer in the Optimus UI. (Bearer requests skip the OAuth browser flow entirely — for browser sign-in, use the org-agnostic _ URL above instead.)

Claude.ai, Claude Desktop & Cowork

These apps connect to the same Fynd MCP server as a custom connector (a remote MCP URL) rather than via the plugin marketplace. The same steps work in all three:

1. Open Settings → Connectors → Add custom connector (open it on claude.ai).
2. Name it Fynd and paste the Fynd MCP URL: https://console.fynd.com/organization/_/autonomous/mcp/v1
3. Click Add, then sign in in your browser — if you belong to more than one organization, pick one on the consent screen.

The URL must be HTTPS and reachable from the public internet (Anthropic's servers connect to it directly, so a localhost URL won't work). Custom connectors are available on Claude.ai, Claude Desktop, and Cowork (Free plan and up; in beta) — see Anthropic's custom connector guide.

Codex (OpenAI)

Codex connects to the same Fynd MCP server through its config.toml (no marketplace). See codex/config.toml and codex/AGENTS.md.

1. Add the server — copy the block into ~/.codex/config.toml (or a trusted project's .codex/config.toml):

   [mcp_servers.fynd]
   url = "https://console.fynd.com/organization/_/autonomous/mcp/v1"
   enabled = true
   startup_timeout_sec = 20

2. Sign in — codex mcp login fynd opens your browser; pick your organization at the consent screen (no token to paste).
3. (Optional) Guidance — append codex/AGENTS.md to your project's AGENTS.md. Codex uses AGENTS.md rather than SKILL.md, so this mirrors the getting-started + context-resolution skills in Codex-native form.

Other agents (Copilot, Gemini, Cursor, …)

These connect to the same Fynd MCP server — point your agent's MCP config at your Fynd MCP URL (OAuth, or a Bearer token as in the Claude Code section). The skills/ here are portable SKILL.md files for agents that support that format; for others, the codex/AGENTS.md guidance is a good plain-markdown starting point. Platform-native manifests (e.g. .github/plugin.json for Copilot) land here over time.

What you can do

Ask naturally — e.g. "show today's pending shipments", "create a Holi sale collection", "list active coupons", "draft a blog post about the new arrivals". The full Fynd commerce tool catalogue is available, and new tools appear automatically as the platform adds them.

For deeper domain rules and status flows, the agent can consult the bundled knowledgeSearch tool (e.g. OMS shipment lifecycle, collection types). Two skills ship here and activate automatically: getting-started (how to discover and use the commerce tools) and context-resolution (how the agent picks the right company/storefront for an action).

Support

Issues: file against the Optimus repository. Contact: developers@gofynd.com.