Genseo

View saved version →

---
name: genseo
description: Use Genseo through its remote MCP server to inspect AI visibility, tracked prompts, cited sources, competitors, projects, keywords, SEO drafts, audits, publishing integrations, and webhooks.
---

# Genseo

Use the connected Genseo MCP tools instead of calling internal application routes or the database.

## Workflow

1. Call `genseo_me` and `genseo_projects_list` before any project operation.
2. Ask the user to select exactly one accessible project when the intended project is not already explicit. Never guess a project ID or silently switch projects.
3. Include the selected `project_id` with every project operation.
4. Read an existing post before updating it and send only intentional changes.
5. For AI visibility questions, start with `genseo_visibility_overview`; use the prompt-list and prompt-detail tools only when the user asks for prompt-level evidence.
6. Prefer creating a draft before generating or publishing content.
7. Check `genseo_integrations_list` before publishing.
8. Ask for confirmation before `genseo_posts_publish` unless autonomous publishing was explicitly requested.

Treat authorization and project-boundary errors as final. OAuth access never includes billing, team management, credentials, or project deletion. Viewer roles stay read-only, and writes require Agent Autonomy. Back off on rate limits, and treat `202 Accepted` as successful queueing.

For endpoint details and error codes, use [the Genseo developer documentation](https://docs.genseo.co/developers/overview).

View saved version →

---
name: genseo-setup
description: Configure or troubleshoot the Genseo remote MCP connection for ChatGPT, Codex, Claude, Cursor, or Grok. Use when Genseo tools are disconnected, authentication is missing, or the user asks how to connect Genseo.
---

# Set up Genseo

1. Connect the remote server at `https://api.genseo.co/mcp` and complete the browser-based Genseo OAuth flow.
2. Review the requested scopes and approve the connector only if the client name and callback are expected.
3. Reload the plugin and open `/mcp` to verify the `genseo` server connection.
4. Call `genseo_me` and `genseo_projects_list`, then select one project before using another Genseo tool.

For non-interactive developer or CI use only, a project-bound `GENSEO_API_KEY` can be sent as a Bearer token. Never paste the key into chat, source files, public manifests, or version control. Public installations use OAuth 2.1.

For setup details, use [the Genseo developer documentation](https://docs.genseo.co/developers/overview). Contact `support@genseo.co` if authentication fails after creating a new key.