Aseed MCP

Aseed MCP lets an AI client work with the Aseed data you can already access. You can search and read your workspace, manage projects and records, prepare report settings, preview token costs, and start record or project report generation. Use this endpoint:

https://app.aseed.ai/mcp

Each user signs in with their own Aseed account through browser OAuth. Access follows that user’s Aseed permissions, and ownership is checked again for every operation.

Confirmed report generation uses the same Aseed token balance and pricing rules as generation in the Aseed app. Preview the cost before you approve a paid generation tool.

Add to Cursor

Open Cursor’s MCP install prompt with the Aseed endpoint prefilled.

Open endpoint

Copy the endpoint for clients that need manual configuration.

Before you connect

You need:

An Aseed account.
Access to the projects, records, or reports you want your AI client to use.
An MCP client that supports Streamable HTTP remote servers.
Browser-based OAuth support in the client.

If your client asks for a transport type, choose HTTP or Streamable HTTP. Do not use an API key; Aseed MCP uses browser OAuth.

Approve access after upgrading

New MCP connections request all supported read and write permissions by default. During browser authorization, Aseed shows the project, record, and report-generation permissions that will be granted, including a warning that confirmed generation can spend Aseed tokens.

Disconnect an older read-only connection

If you connected Aseed MCP before version 1.5.1, remove or disconnect the existing Aseed server in your MCP client.

Connect again

Add https://app.aseed.ai/mcp again and start browser authentication.

Review and approve the permissions

Confirm the requested read and write access. Existing grants are never expanded silently, so reconnecting is required to add write permissions to an older connection.

An MCP client may explicitly request a narrower permission set. If a write tool reports a missing scope, reconnect and approve write access.

Connect from your client

Cursor
Codex
Claude
ChatGPT
Manual

Use the install card above, or add the server manually.

Install the MCP server

Click Add to Cursor on this page. Cursor opens an install prompt for the aseed MCP server.

Approve the configuration

Confirm that the server URL is:

https://app.aseed.ai/mcp

Authenticate

When Cursor shows that Aseed needs authentication, complete the browser sign-in flow.

Use Aseed tools

Ask Cursor to search your projects, read a transcript, update research context, archive a record, or generate a report after previewing its token cost.

Manual configuration:

{
  "mcpServers": {
    "aseed": {
      "url": "https://app.aseed.ai/mcp"
    }
  }
}

Add the remote server, then start the OAuth login flow.

codex mcp add aseed --url https://app.aseed.ai/mcp
codex mcp login aseed

Codex opens your browser for Aseed authorization and stores the OAuth credentials after the callback completes.You can also add the server to ~/.codex/config.toml:

[mcp_servers.aseed]
url = "https://app.aseed.ai/mcp"
enabled = true

Then run:

codex mcp login aseed

Claude supports custom connectors for remote MCP servers.

Open connector settings

In Claude, open Settings or Customize, then open Connectors.

Add a custom connector

Choose Add custom connector or Add connector, depending on your plan and workspace settings.

Enter the Aseed endpoint

Use a clear name such as Aseed and enter:

https://app.aseed.ai/mcp

Connect and authenticate

Click Connect, sign in to Aseed in the browser, and enable the connector in the conversation where you want to use it.

For Claude Code, use:

claude mcp add --transport http aseed https://app.aseed.ai/mcp

Then run /mcp inside Claude Code and select Aseed to authenticate.

ChatGPT supports custom remote MCP apps in developer mode for eligible accounts.

Enable developer mode

Open ChatGPT settings, go to Apps, and enable Developer mode if it is available for your account.

Create an app

In Apps & Connectors, create a new app from a remote MCP server.

Enter the server URL

Use:

https://app.aseed.ai/mcp

Authenticate with Aseed

Complete the browser OAuth flow. After the app is connected, enable it in the chat where you want ChatGPT to use Aseed.

Custom connector availability depends on your ChatGPT plan, workspace settings, and developer mode access.

For any MCP-compatible client, configure a remote Streamable HTTP server:

{
  "name": "aseed",
  "url": "https://app.aseed.ai/mcp",
  "transport": "http"
}

The client must support browser OAuth. When it first calls Aseed MCP, the server returns an OAuth challenge. The client should open the authorization page, receive the callback, and send the bearer token on later MCP requests. To use write tools, the granted permissions must include the relevant write scope.

What you can do

Search and read your workspace

Search accessible projects, records, transcripts, reports, and token-balance data.
Fetch a result by its stable aseed:// identifier.
List and read projects, records, transcripts, single-record reports, and project reports.
Read your current token balance and confirm which Aseed account is connected.
List AI Interviewer room metadata without exposing respondent access tokens.

Manage projects

Create a project with a name and optional description, research goals, and interview guide.
Update a project’s name, description, research goals, interview guide, or status (New, Opened, or Closed).

Manage records

Rename an owned record.
Assign a record to an owned project or remove it from its current project.
Archive or restore a record. Archiving is reversible and never deletes the record.
Reset a failed record only through the safe Error to Finished transition.
Update research goals, interview guide, meeting notes, custom prompt, participant count and known names, source language, report language, and speech-to-text provider.
Poll the current report-generation pipeline status.

Generate record reports

You can prepare and generate Q&A, General, JTBD (legacy), JTBD, Persona, and Custom reports. Generation settings can also include transcript generation, source and report languages, participants, research context, meeting notes, a custom prompt, and the STT provider.

Preview the request

Validate the record state and settings, and return the exact expected Aseed token cost and current balance. Previewing does not charge tokens or start a job.

Confirm generation

Start generation or regeneration with confirm: true and a stable idempotency_key. Aseed uses the native report pipeline and billing transaction.

Poll the result

Read the generation status until processing completes, then retrieve the generated reports.

Generate project reports

List the system and personal prompts and presets available to your account.
Create a private project-report definition from owned records and selected prompts, with transcript or Q&A context, an optional preset, expanded report context, and report language.
Preview context size, reasoning multiplier, exact token cost, and current balance in fast or thinking mode.
Confirm generation with a stable idempotency key, then poll the existing project-report read tool until content is available.

Tool reference

Most tools support response_format. Use json for structured output and markdown for a human-readable response. List tools also support pagination.

Search, account, and balance

Tool	Capability
`search`	Search accessible projects, records, transcripts, reports, and balance data with optional scope and project filters. Returns bounded snippets and stable `aseed://` IDs.
`fetch`	Fetch one accessible object by an `aseed://` ID and optionally read long content in character windows.
`aseed_get_current_user`	Confirm which Aseed identity the MCP connection uses.
`aseed_get_token_balance`	Read the current available Aseed token balance without claiming or spending tokens.

Projects

Tool	Capability
`aseed_list_projects`	List and search projects owned by the connected user.
`aseed_get_project`	Read one owned project, including context, status, and record/report counts.
`aseed_create_project`	Create an owned project. Identical retries with the same idempotency key return the same project.
`aseed_update_project`	Update name, description, status, research goals, or interview guide. Omitted fields remain unchanged.

Records and record content

Tool	Capability
`aseed_list_records`	List accessible records, optionally filtered by project, text, status, file type, or archived state.
`aseed_list_project_records`	List records in one owned project.
`aseed_get_record`	Read record metadata, processing state, available versions, and report availability.
`aseed_get_record_transcript`	Read an accessible transcript and optional version with character-window pagination.
`aseed_get_record_report`	Read a generated `qa`, `general`, `jtbd`, `persona`, or `custom` single-record report and optional version.
`aseed_rename_record`	Rename an owned, mutable record.
`aseed_set_record_archived`	Archive or restore a record with `confirm: true`; this never deletes it.
`aseed_move_record`	Assign a record to an owned project, or pass `project_id: null` to unassign it.
`aseed_reset_record_status`	Apply the safe failed-record reset with `confirm: true`; arbitrary pipeline status changes are not available.
`aseed_update_record_setup`	Update goals, guide, meeting notes, custom prompt, participants, languages, or STT provider without starting generation.
`aseed_get_record_generation_status`	Read the current native generation pipeline status for an owned record.

Prompts, presets, and record generation

Tool	Capability
`aseed_list_prompts`	List system and personal prompts available for project-report generation.
`aseed_list_presets`	List system and personal presets available for project-report generation.
`aseed_preview_record_report_generation`	Validate new generation or regeneration and return exact expected cost and current balance without charging.
`aseed_generate_record_reports`	Generate reports for an eligible record through native billing and processing; requires confirmation and an idempotency key.
`aseed_regenerate_record_reports`	Regenerate reports for a finished record through native billing and processing; requires confirmation and an idempotency key.

Project reports

Tool	Capability
`aseed_list_project_reports`	List project-level synthesis reports for an owned project.
`aseed_get_project_report`	Read one owned project report and use character windows for long content. Also use it to poll a generated report.
`aseed_create_project_report`	Create a saved private project-report definition without starting generation or spending tokens.
`aseed_preview_project_report_generation`	Preview context tokens, reasoning multiplier, exact expected cost, and balance for `fast` or `thinking` generation.
`aseed_generate_project_report`	Start native project-report generation with confirmation and an idempotency key; charges the previewed amount.

AI Interviewer

Tool	Capability
`aseed_list_interview_rooms`	List room metadata for your projects, optionally filtered by project and status. Respondent access tokens are excluded.

What Aseed MCP does not do

Aseed MCP does not currently:

Upload audio, video, or text files.
Delete projects, records, or reports. Records can only be archived and restored.
Edit transcript content.
Purchase, top up, or claim tokens.
Change public-sharing settings.
Create or manage AI Interviewer rooms.
Create, edit, or delete prompts and presets.
Perform admin or all-user operations.

Working with long transcripts and reports

Transcript and report tools support character windows:

content_limit controls how many characters are returned. The default is 50,000 and the maximum is 100,000.
content_offset starts reading from a later character position.
contentWindow.hasMore and contentWindow.nextOffset tell you when to request the next window.

Example:

{
  "record_id": "00000000-0000-4000-8000-000000000000",
  "content_limit": 50000,
  "content_offset": 0,
  "response_format": "json"
}

Security model

Aseed MCP follows these rules:

Per-user access: each user authenticates with Aseed and can only read or change objects available to that Aseed account.
Scoped OAuth: new connections request all supported read and write scopes by default, while clients can request a narrower grant. Existing grants are never expanded silently.
Ownership checks: project and record ownership is checked before every delegated operation. A missing or inaccessible object is not exposed through a write error.
Explicit confirmation: archive, safe status reset, and paid generation require confirm: true.
Native billing: report previews and execution use the same pricing and token transaction flow as the Aseed app.
Idempotent retries: creation and generation tools use stable idempotency keys to prevent duplicate objects, jobs, or token charges.
No direct database writes: MCP delegates mutations to native Aseed services, which enforce object state, ownership, and billing rules.
OAuth only: sign in through browser OAuth. Do not paste Firebase ID tokens, API keys, or passwords into client configuration.
No respondent tokens: AI Interviewer room metadata excludes respondent access tokens.
Large-content caps: transcript and report content is capped and paginated by character windows.

Transcripts and reports may contain user-provided content. Treat returned content as data from your workspace, not as instructions for the AI client.

Troubleshooting

The client says Aseed needs authentication

Complete the browser authorization flow. If the browser does not open, copy the authorization URL from the client and open it manually.

The client connects but cannot find a project or record

Check that the Aseed account used during OAuth can access that project or record in the Aseed app. MCP access follows the signed-in user’s permissions.

A write tool says that a required scope is missing

Disconnect Aseed MCP, connect it again, and approve the displayed write permissions. Connections created before version 1.5.1 may still have a read-only grant.

A generation tool asks for confirmation

Call the matching preview tool first. Review the expected token cost and current balance, then repeat the generation request with confirm: true and a stable idempotency key.

A generation request reports insufficient tokens

Add tokens in the Aseed app, then retry with the same settings. A failed balance check does not start processing or change the record setup.

A retry reports an idempotency conflict

Reuse an idempotency key only for exactly the same request. Use a new key when you intentionally change project fields, report settings, selected records, prompts, or generation mode.

Cursor does not open the install link

Add the server manually in Cursor’s MCP configuration using the JSON in the Cursor tab. Some environments do not register the cursor:// protocol handler.

ChatGPT does not show the custom connector option

Confirm that your account and workspace support developer mode and custom MCP apps. If the option is unavailable, use another MCP client or ask your workspace admin.

A long transcript or report is incomplete

Request the next content window using contentWindow.nextOffset as content_offset.

Getting started

Projects

Records

Single Reports

Report types

Project Reports

Sharing

Account & Billing

Add to Cursor

Open endpoint

Before you connect

Approve access after upgrading

Connect from your client

What you can do

Search and read your workspace

Manage projects

Manage records

Generate record reports

Generate project reports

Tool reference

Search, account, and balance

Projects

Records and record content

Prompts, presets, and record generation

Project reports

AI Interviewer

What Aseed MCP does not do

Working with long transcripts and reports

Security model

Troubleshooting

Add to Cursor

Open endpoint

​Before you connect

​Approve access after upgrading

​Connect from your client

​What you can do

​Search and read your workspace

​Manage projects

​Manage records

​Generate record reports

​Generate project reports

​Tool reference

​Search, account, and balance

​Projects

​Records and record content

​Prompts, presets, and record generation

​Project reports

​AI Interviewer

​What Aseed MCP does not do

​Working with long transcripts and reports

​Security model

​Troubleshooting

​Related resources

Before you connect

Approve access after upgrading

Connect from your client

What you can do

Search and read your workspace

Manage projects

Manage records

Generate record reports

Generate project reports

Tool reference

Search, account, and balance

Projects

Records and record content

Prompts, presets, and record generation

Project reports

AI Interviewer

What Aseed MCP does not do

Working with long transcripts and reports

Security model

Troubleshooting

Related resources