Iteratio

Agent workflow

How to create prepared language cards with the Iteratio MCP server

The Iteratio Cards MCP server is designed for prepared learning material: the agent fills the card fields before creation instead of relying on silent enrichment afterward.

  • Use OAuth with PKCE instead of sharing Firebase tokens
  • Prepare card content before module creation
  • Check existing vocabulary and add exercises through documented tools

Guide steps

From source material to review

01

Connect a compatible remote MCP client

Configure the documented endpoint at https://iteratio.app/api/mcp in a client that supports remote HTTP MCP servers and OAuth.

02

Approve limited account access

Complete the browser authorization flow with your Iteratio account. The client receives a scoped MCP access token; do not paste Firebase ID tokens into agent chats or configuration files.

03

Prepare useful card fields

Ask the agent to provide the term, translation, and other required or useful context before creation. Follow the tool contract for examples, descriptions, images, and language direction.

04

Create unique material and exercises

Use the documented uniqueness-aware flow when you want to avoid vocabulary already visible to the account, then create exercises after the module is available when that matches the learning goal.

Questions

Frequently asked questions

Does MCP automatically enrich incomplete cards later?

No. The calling agent must prepare the card content before module creation.

Does the agent receive my Firebase token?

No. The OAuth flow issues a separate scoped Iteratio MCP access token after browser approval.

Can MCP avoid vocabulary I already have?

The documented create_unique_module flow checks candidate terms against vocabulary already visible to the user before creating the module.

Explore