Cursor
Add FLORA MCP to Cursor via config file or one-click install.
Option A — Config file (recommended)
Section titled “Option A — Config file (recommended)”Add FLORA to your global Cursor MCP config so it’s available in every project.
Edit ~/.cursor/mcp.json (create the file if it doesn’t exist):
{ "mcpServers": { "flora": { "url": "https://florafauna-ai.stlmcp.com/" } }}Restart Cursor. Open Cursor Settings → MCP — flora should be listed with a green status dot. Click Connect to start the OAuth flow.
Option B — Project-only
Section titled “Option B — Project-only”For a Cursor MCP config scoped to one repo, use .cursor/mcp.json at the project root instead. Commit it so teammates pick it up automatically.
{ "mcpServers": { "flora": { "url": "https://florafauna-ai.stlmcp.com/" } }}Authorize
Section titled “Authorize”The first time a Cursor agent calls a FLORA tool, Cursor opens a browser for the OAuth flow. Sign in with your FLORA account and approve. The token is stored in Cursor’s secure credential store.
Verify
Section titled “Verify”In a Cursor chat, ask:
List my FLORA Techniques.
Cursor’s agent will request permission to call list_techniques. Approve once; subsequent calls remember the choice.
Remove
Section titled “Remove”Delete the flora entry from ~/.cursor/mcp.json (or the project’s .cursor/mcp.json), restart Cursor, then revoke the token in FLORA → Settings → Connected apps.
Troubleshooting
Section titled “Troubleshooting”- Status dot is red — usually the URL is wrong or your network blocks
*.stlmcp.com. Double-check the URL is exactlyhttps://florafauna-ai.stlmcp.com/with the trailing slash. - OAuth doesn’t open — Cursor sometimes needs a manual click. Look for a notification toast with an authorization link.
- Tools don’t appear in the agent — toggle the
floraserver off and on in Settings → MCP. Some Cursor versions require a refresh after the first connection.