ActionKit MCP Starter

@useparagon

代码仓库

基本信息

分类

开发工具

传输方式

stdio

作者

useparagon

关于 ActionKit MCP Starter

Starter code for a MCP server powered by ActionKit

ActionKit MCP Starter 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "mcp-actionkit": {
      "command": "node",
      "args": [
        "ABSOLUTE_PATH/mcp-actionkit/build/index.js"
      ],
      "env": {
        "USER": "",
        "PARAGON_PROJECT_ID": "",
        "SIGNING_KEY": ""
      }
    }
  }
}

ActionKit MCP Starter 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

工具是从 README 中自动提取的。维护者可以在 ## Tools 标题下列出工具,即可填充这部分内容。

概览

What is ActionKit MCP Starter?

ActionKit MCP Starter is an MCP server that demonstrates ActionKit, giving Claude Desktop or Cursor access to all of ActionKit’s Slack actions. It is intended for developers who want to integrate Slack tools into AI assistants using Paragon for authentication.

How to use ActionKit MCP Starter?

Clone the repo, run npm install and npm run build, then configure your Claude Desktop or Cursor config file with the absolute path to build/index.js and fill in the USER, PARAGON_PROJECT_ID, and SIGNING_KEY environment variables with your Paragon credentials. The user must authenticate to Slack via the Paragon Connect Portal (e.g., demo.useparagon.com) before using the tools.

Key features of ActionKit MCP Starter

Provides Slack actions through MCP protocol
Works with both Claude Desktop and Cursor
Uses Paragon Connect Portal for user authentication
Defaults to Slack actions only (filter removable)
Quick setup via npm and config files

Use cases of ActionKit MCP Starter

Interacting with Slack from Claude Desktop using natural language
Enabling Slack actions inside Cursor’s AI workflows
Demonstrating ActionKit’s integration capabilities with AI assistants

常见问题

What dependencies does ActionKit MCP Starter require?

You need Node.js and npm installed, a Paragon project with credentials, and a user authenticated to Slack via the Paragon Connect Portal.

How does authentication work?

The server assumes the user has authenticated via the Paragon Connect Portal. The `USER` env variable corresponds to the logged-in user, and Slack must be authenticated there for the tools to work on your behalf.