MCP setup
Let your agents request content packs.
LetsAskIt exposes a Model Context Protocol server over streamable HTTP at:
POST https://letsaskit.com/mcp
Requirements
- Team tier API key — MCP needs a team key; Pro keys get a
403. - Auth:
Authorization: Bearer <team-api-key> - Headers:
Content-Type: application/jsonandAccept: application/json, text/event-stream(per the MCP spec).
Getting a key — and trying it free
API keys are issued by the operator and shown once at issue (only the SHA-256 hash is stored). To get one, email [email protected] from the address that will own the subscription; the reply carries your key and the checkout step. Paying then happens on the hosted Stripe checkout started with that key, and the plan activates on the key automatically when the payment completes — see Pricing for the plain-terms buying notes. Directory reviewers receive a scoped reviewer key on request via the same address.
No key yet? The Free tier is the keyless Studio (letsaskit.com/studio): 30 jobs a month and one voice profile, no sign-up and no key. MCP itself needs a Team key; the free Studio is how you try the workflow before subscribing.
Tools
| Tool | What it does |
|---|---|
create_pack | Run the full pipeline: normalize input → generate per format → quality gate → content pack. |
create_from_url | Fetch a URL (article HTML), summarize it, create a pack. |
create_from_transcript | Create a pack from raw transcript text. |
list_voice_profiles | List the voice profiles on the key. |
get_job_status | Check a job's state and retrieve its pack. |
Example
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "create_pack",
"arguments": {
"input_type": "brief",
"content": "The quiet math of wealth: automate a high savings rate into low-fee index funds.",
"formats": ["summary", "linkedin_post"]
}
}
}