creatoros-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CREATOROS_API_KEY | No | Optional CreatorOS Developer Pass key for Pro tier access and higher rate limits. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| creatoros_extractA | Extracts readable main content from any public web page URL and converts it into clean, noise-free Markdown optimized for LLM context, summarization, and RAG pipelines. Strips advertisements, navigation headers, cookie banners, and scripts while preserving headings, lists, tables, and code blocks. When to use:
When NOT to use:
Behavior:
|
| creatoros_searchA | Executes an autonomous live web search for fresh information and automatically extracts deep Markdown content from the highest-ranking search result pages. Combines web search retrieval and web scraping in a single step for AI agents. When to use:
When NOT to use:
Behavior:
|
| creatoros_speakA | Converts English text into natural, studio-quality speech audio with human inflection and cadence using the CreatorOS Neural Voice Studio. Returns a playable audio URL or audio stream. When to use:
When NOT to use:
Behavior:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct capability: URL-to-Markdown extraction, query-based web search, and text-to-speech. The descriptions explicitly cross-reference each other ('use creatoros_search instead', 'use creatoros_extract instead'), leaving no realistic path for misselection even where extract and search both return Markdown.
All three tools use the same creatoros_ prefix followed by a single clear verb (extract, search, speak). No mixing of camelCase, noun-phrases, or version suffixes; the pattern is fully predictable.
Three tools is on the lean side but each covers a genuinely separate operation with no filler or redundant variants. Slightly thin for a server branded as a general 'creator' platform, but well-scoped for the read-and-speak niche it actually covers.
The read (extract/search) and output (speak) lifecycle is fully covered with no dead ends within the stated scope, and read-only behavior is explicit. Minor gaps exist—no batch/multi-URL extraction, no summarization or caching of fetched content—but agents can work around these by chaining calls.