MCP directories are full of narrow tools that do one thing. Iteration Layer gives MCP users the European AI workflow runtime for documents, images, websites, spreadsheets, and generated files that can feed each other in one assistant session.
Zero data retention
Made & hosted in the EU
100 trial credits
One output feeds the next
APIs that cover every step of EU content workflows — ingestion, transformation, generation, and exports. One key, one credit pool, and structured JSON responses designed to chain together.
Extract inputs
Turn documents, websites, and other sources into structured output.
Native SDKs for TypeScript, Python, and Go. OpenAPI spec for everything else. MCP server for AI agents and Claude Code skills. n8n integration for visual workflows.
EU AI workflow runtime
Run document, image, and file steps through one EU-hosted workflow layer with shared API conventions and billing.
You're dealing with this every day
Here's what changes when you stop juggling tools and start building pipelines.
Directories list narrow tools
Many MCP servers expose one useful action but stop there. Real content work needs extraction, conversion, image processing, and generated output in the same tool set.
Multiple tools, one server
Document extraction, document-to-markdown, website extraction, image transformation, document generation, image generation, and sheet generation are exposed through one MCP server.
Tool outputs do not connect
When teams lack an approved agent toolkit, client files move through whatever parser, chat tool, or generator gets the work done first.
Typed outputs assistants can use
Tools return structured JSON, clean Markdown, generated files, and predictable errors so your assistant can inspect results and decide the next step without guessing.
Tool outputs do not connect
A document tool returns text, an image tool returns a file, and a generation tool expects structured input. The assistant needs predictable schemas between steps, not disconnected actions.
Interactive now, API later
Start in Claude, Cursor, or Windsurf through MCP. When the workflow becomes part of a product or backend job, use the same credentials and credit pool through REST or SDKs.
Real-world pipelines, ready to ship
Each recipe chains multiple APIs into a complete workflow. Pick one, tweak it, and deploy — or use it as a starting point for your own pipeline.
Your data is processed on EU-hosted infrastructure and never stored beyond temporary logs. Zero data retention, GDPR-compliant workflows, and a Data Processing Agreement are available for every customer.
Learn more about our security practices
.
EU-hosted core processing
Application and processing infrastructure runs in Europe, with provider-scope ISO 27001 and BSI C5 evidence documented for procurement reviews.
Zero data retention
Customer files and processing results are not stored after the request. Usage logs are retained for 90 days and automatically deleted.
Clear answers for security teams
Give reviewers the answers they need up front: where files are processed, what is retained, which subprocessors are involved, and how AI inputs, outputs, review gates, and audit records move through each workflow.
The AI Agents page is for teams building agent systems and production toolchains. This page is for people discovering Iteration Layer through MCP directories who want to connect one useful server to Claude, Cursor, Windsurf, or another MCP client.
Which MCP clients can I use?
The hosted server uses Streamable HTTP MCP with OAuth 2.1. It works with compatible clients such as Claude, Cursor, Windsurf, and other MCP clients that support remote HTTP servers. See the MCP setup docs.
What tools does the MCP server expose?
It exposes workflow tools for document extraction, document-to-markdown, website extraction, image transformation, document generation, image generation, and sheet generation through one authenticated server.
Can MCP tools chain together in one assistant session?
Yes. An assistant can extract data from a PDF, convert supporting files to Markdown, process an image, generate a PDF summary, and export rows to XLSX using the same server and credit pool.
Do I need API keys inside my MCP client?
No. The hosted MCP server uses OAuth 2.1, so your MCP client opens a browser authorization flow. You do not paste long-lived API keys into client settings.
Can I move from MCP to production API usage?
Yes. MCP is useful for interactive work and prototyping. The same operations are also available through REST, OpenAPI, and the TypeScript, Python, and Go SDKs when you want to ship the workflow in production.
Build your first workflow in minutes
Chain our APIs into a workflow you can test with your own data during the 7-day trial.