Kakao Bot Mcp Server

Created By
inspirit941a year ago
MCP Server Implementation on Kakao Developers API to connect an AI Agent
Overview

What is Kakao Bot MCP Server?

Kakao Bot MCP Server is an implementation of the Model Context Protocol (MCP) that integrates the Kakao Developers API to connect an AI Agent to the Kakao Official Account.

How to use Kakao Bot MCP Server?

To use the Kakao Bot MCP Server, you need to create a Kakao application, set up your local environment, and run the server with the necessary configurations. Follow the installation steps provided in the documentation.

Key features of Kakao Bot MCP Server?

  • Integration with Kakao Developers API for AI Agent connectivity.
  • Support for sending various types of messages (text, feed, list, location, calendar, commerce) through Kakao Talk.
  • Customizable message templates for different use cases.

Use cases of Kakao Bot MCP Server?

  1. Sending automated messages to users via Kakao Talk.
  2. Integrating AI functionalities into Kakao Official Accounts.
  3. Creating personalized communication experiences for users.

FAQ from Kakao Bot MCP Server?

  • Is this project officially supported by Kakao?

No, this repository is not officially provided or maintained by Kakao.

  • What are the requirements to run this server?

You need Python 3.13+ and a Kakao account to use this server.

  • Can I use this server for personal projects?

Yes, but be aware that Kakao's API permissions are primarily managed at the business application level.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
inspirit941
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago