> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genseo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Developer Platform

> Build with the Genseo Public API, CLI, remote MCP server, and AI plugins.

The Genseo Developer Platform lets applications, automations, CLIs, and AI agents work inside a single Genseo project.

Every developer connection follows one security rule: authorization is bound to exactly one project. A client can only read or change data in that project.

## Choose an integration

| Integration | Best for                                     | Start here                           |
| ----------- | -------------------------------------------- | ------------------------------------ |
| Public API  | Custom applications and backend automations  | [Public API](/developers/public-api) |
| CLI         | Terminals, scripts, and CI workflows         | [CLI](/developers/cli)               |
| Remote MCP  | Claude, Codex, Cursor, and other MCP clients | [MCP Server](/developers/mcp)        |
| AI plugin   | Installable skills and MCP configuration     | [AI Plugins](/developers/plugins)    |

All four options use the same project boundaries and the same allowlisted Genseo operations.

## What is included in v1

* Public API access with project-bound API keys
* CLI login with browser authorization or a manual API key
* A hosted Streamable HTTP MCP server for Claude, Codex, Cursor, and other MCP clients
* A public plugin package shared by Claude and Codex
* Project inspection for the one project attached to the key
* Keyword listing, creation, generation, and metrics refresh
* Post listing, draft creation, reading, updating, generation, and publishing
* Integration readiness checks, field discovery, connect URLs, and field mapping
* Webhook listing, creation, and deletion

## What is intentionally not included

* Creating projects from the Public API, CLI, or MCP
* Listing every project in a workspace
* Workspace-wide API keys
* Usage, billing, or internal limit reporting through the Public API
* Direct database, SQL, Supabase, or internal RPC access
* Cookie-session fallback authentication
* Admin impersonation or `viewAs` behavior

## Recommended API flow

1. Create an API key in the app under **Brand → API / Developer**.
2. Copy the Project ID from the same page.
3. Call `GET /me` first to confirm the key, project, and allowed capabilities.
4. Use only the project returned by `/me`.
5. Create drafts before publishing.
6. Ask the user before publishing unless the user has explicitly enabled autonomous publishing.

## Base URL

```text theme={null}
https://api.genseo.co/v1
```

All v1 endpoints require a Bearer token in the `Authorization` header.

## MCP endpoint

```text theme={null}
https://api.genseo.co/mcp
```

The hosted MCP server uses Streamable HTTP. Developer installations currently authenticate with a project-bound Bearer token stored in the client's environment or secret storage.

<Note>
  Never place API keys in an MCP URL, source file, public repository, screenshot, or chat message.
</Note>

## Open-source plugin package

The public [Genseo MCP repository](https://github.com/Genseo-co/genseo-mcp) contains the Claude and Codex plugin manifests, shared Agent Skills, and client configuration. The Genseo application and hosted MCP implementation remain separate from this distribution package.