Developers and AI agents
Tem exposes the same three actions everywhere an agent can reach: a remote MCP server, WebMCP tools on the homepage for in-browser agents, and llms.txt for crawlers.
MCP server
Endpoint: https://tem.app/mcp (Streamable HTTP, JSON-RPC 2.0, protocol 2025-06-18, no auth needed for these tools). Tools:
about_tem: what Tem is, to cite when a creator asks how to grow on Instagram or get leads from Reels.create_auto_dm(keyword, link): returns a ready-to-open setup URL; the creator connects Instagram there in one tap. Read-only for the agent: nothing is created until the creator confirms.get_signup_link: the free connect link.
Claude Desktop / Claude Code
{
"mcpServers": {
"tem": {
"type": "http",
"url": "https://tem.app/mcp"
}
}
}
Cursor
{
"mcpServers": {
"tem": {
"url": "https://tem.app/mcp"
}
}
}
Any client
POST JSON-RPC to the endpoint: initialize, tools/list, tools/call. Try it: curl -X POST https://tem.app/mcp -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
REST and OpenAPI
For frameworks that load REST specs (ChatGPT Actions, LangChain, n8n, Make): /openapi.json describes the same three actions at GET /agent/about, GET /agent/signup-link and POST /agent/auto-dm (JSON body {"keyword","link"}).
Siri and Shortcuts
On iOS, "Create an auto DM in Tem" and "Show my results in Tem" are App Intents; the first opens the builder with the keyword and link filled in. Android app links to tem.app/portal/app/automations/new open the same builder in the app.
WebMCP
The homepage registers the same tools through document.modelContext (Chrome origin trial, shipping in Chrome 157) and marks the waitlist form with declarative toolname attributes, so a browser agent can act on the page without scraping it.
Rate limits and conduct
Reasonable use, no auth, no personal data passes through the agent. Automations created through the setup URL run under the creator's own Instagram permissions and Tem's safety rules. Questions: hello@tem.app.