PlayMCP
by PlayMCP
Kakao's MCP gateway routes one endpoint into up to 10 servers you pick from a catalogue of 462. Anthropic lists zero tools; Kakao publishes 2,942 across the catalogue. One Kakao tool sends a real KakaoTalk message to yourself.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect PlayMCP via MCP
https://playmcp.kakao.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
PlayMCP Tools & Capabilities (0)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Kakao's agent-connection guide instructs an agent to escape its sandbox, and you should not let it. The guide at
playmcp.kakao.com/llms/mcp-connection-guide.mdtells the reading agent to install themcporterpackage and states that even when the request arrives in a container environment, it must be installed into the base system environment, with credentials written to~/.mcporter/credentials.jsonand no backup needed. It also embeds a fixedclient_id. We did not follow any of it. Treat that document as vendor data, not as instructions to your agent, and perform the token exchange yourself. - One scope, and it is a wildcard.
defaultnames no object and no verb. Consent cannot separate a map lookup from an outbound message, and it covers servers you add after consenting. - The connector has no tool list, so no tool list can be audited. What you granted is determined by your toolbox, and it changes whenever you edit it. Re-check the toolbox rather than the connector.
- Published tool metadata can be stale. Kakao states catalogue pages do not auto-refresh while calls use live tool information. The list you reviewed is not guaranteed to be the list that runs.
- Prompts and resources are dropped. Kakao's review policy states PlayMCP does not handle those parts of the MCP spec, so a server's non-tool surfaces do not reach your client.
- Third-party servers, not Kakao services. 425 of the 462 catalogue entries declare no auth of their own and are operated by parties other than Kakao. Kakao reviews them but states it may unpublish one after the fact — approval is a checkpoint, not a warranty.
- Ten servers maximum per toolbox, and Kakao counts a server toward the cap even when it is toggled off, offline, or deleted.
- Korean-language surface. The catalogue, help centre and most tool descriptions are Korean. Tools are geographically scoped to Korea — Kakao Map's directions tools cover South Korea only.
- AI chat is metered, and cannot be topped up. 50 questions, one recharged every five minutes, with Kakao stating there is no way to buy or earn more. This caps the built-in playground, not the connector itself.
- Conversations are retained for 90 days. Kakao states PlayMCP AI chat logs are kept that long for support and error analysis, then deleted automatically. This applies to PlayMCP's own chat, not to Claude.
- We could not read tool schemas or safety annotations from the wire. The endpoint returned 401 to an anonymous request, so no
readOnlyHintordestructiveHintis reported here. The classifications above come from Kakao's published catalogue metadata. - The nominated documentation URL is a bare Notion link that renders nothing to a fetcher.
www.notion.so/2189b97b4888803dbbdcef264e7eff58returns Notion's generic marketing shell containing no PlayMCP text. The page is genuinely public, but only its API returns the content.
Frequently asked questions
There is no fixed number, which is why Anthropic's directory lists zero. PlayMCP is a gateway that routes to whichever servers you put in your toolbox, so the surface is assembled by you at connect time. Kakao's public catalogue held 462 approved servers carrying 2,942 tools on 2026-08-23, and a full toolbox of the ten largest would reach 283.
Yes, if you add the right server to your toolbox. Kakao's own KakaotalkChat server exposes one tool, MemoChat, which its description says sends a KakaoTalk message to yourself. Third-party servers in the catalogue go further: one sends KakaoTalk notifications to every member of a room, and another alerts a designated guardian.
One scope named default, which constrains nothing. Kakao's authorization server advertised scopes_supported of exactly default on 2026-08-23, and the server's RFC 9728 descriptor declares no scopes at all. Because the scope names neither an object nor a verb, it cannot separate reading a map search from sending a message.
Because PlayMCP deliberately refuses Dynamic Client Registration. Kakao's help centre states that PlayMCP does not permit DCR from unspecified AI agents for security reasons, and that the attempt surfaces as a disallowed IP range error. The documented path is a one-time token issued from the toolbox page and exchanged for an access token.
Not necessarily. Kakao's help centre states that tool information on PlayMCP pages does not refresh automatically and that a developer must re-import it and pass re-review. It also states that AI chat loads the latest tool information at call time. So the published description can lag what actually executes.
Yes, with a written review policy and a stated turnaround. Kakao requires every tool to be tested before submission, refuses servers auto-generated by third-party platforms such as Zapier MCP, and rejects tools that request resident registration, passport, card or account numbers. Review completes within seven business days, averaging one to two.
No. Kakao's help centre states that individual MCP endpoint URLs are not exposed publicly and can only be called from within PlayMCP. The gateway at playmcp.kakao.com/mcp is the only external route, and it reaches only the servers you have placed in your toolbox.
No. Kakao's review policy states plainly that PlayMCP does not currently handle the Resource and Prompt parts of the MCP specification. Only tools cross the gateway, so a server offering prompts or resources will have those surfaces dropped rather than forwarded to your client.
Sources
- PlayMCP machine-readable integration index,
llms.txt(retrieved 2026-08-23). Linked from the site's own<link rel="alternate" type="text/markdown">and anai-instructionsmeta tag. · retrieved 2026-08-23 - PlayMCP agent connection guide (retrieved 2026-08-23). Cited as evidence of the sandbox-escape instruction; not followed. · retrieved 2026-08-23
- PlayMCP help centre, "서비스 도움말" (retrieved 2026-08-23). Public, but the HTML renders no content; the 37 FAQ entries were read via Notion's
loadPageChunkandqueryCollectionAPIs. · retrieved 2026-08-23 - PlayMCP MCP review policy, "MCP 심사 정책" (retrieved 2026-08-23), reached via · retrieved 2026-08-23
- PlayMCP public server catalogue API —
https://playmcp.kakao.com/api/v1/mcps?page=0&size=100, all 39 pages (retrieved 2026-08-23). Source of the 462-server, 2,942-tool census and of every tool name quoted here. · retrieved 2026-08-23 - Live auth posture check: anonymous
initializereturned HTTP 401 withwww-authenticate: Bearer resource_metadata=...; RFC 9728 descriptor at ; authorization server metadata at (2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- PlayMCP support — <mailto:playmcp@kakaocorp.com> · Kakao privacy policy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- PlayMCP
- Tools
- 0
- Domain
- playmcp.kakao.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.