Cursor EOD

A powerful MCP server for Cursor and VS Code that summarizes your daily work and posts formatted updates directly to Slack.

typescript

GitHub Stars

typescript

Language

7 months ago

First Indexed

3 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "sackeydavid-cursor-eod-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@techhalo/cursor-eod-mcp"
      ],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-your-bot-token",
        "SLACK_USER_TOKEN": "xoxp-your-user-token-or-empty",
        "SLACK_DEFAULT_CHANNEL": "halo"
      }
    }
  }
}

This MCP server lets you push your end-of-day (EOD) updates to Slack, so you can post a concise summary of what happened in your workspace directly to a Slack channel. It supports both Cursor and VS Code workflows via the MCP, enabling quick one-off updates or automated daily notes through your IDE integration.

How to use

In practice, you connect your MCP client (Cursor or VS Code with Copilot) to the EOD MCP server, configure Slack credentials and a target channel, and then send an EOD status message with a few optional details. The server automatically builds a readable summary from your conversations and posts it to the channel you choose. You can adjust the channel, content, and formatting to match your team’s preferences.

How to install

Prerequisites you need to have before installing: Node.js 18 or newer.

Choose your integration path and follow the setup that matches your editor.

Option A — Cursor (npx based installation) and one-click setup: you install the MCP server inside Cursor and then configure Slack tokens in your MCP configuration.

Option B — Manual Cursor setup (config file) and start with npx.

Option C — VS Code setup (stdio server) using Copilot chat to access MCP commands.

Option D — Clone and run locally (build and start) if you prefer a local development flow.

Additional sections

Configuration and tokens you will work with: Slack bot token (required to post) and optional Slack user token if you want messages posted under your own name/photo. Tokens must be kept private and not committed to any repository.

Key commands you can run from within your MCP client or Copilot Chat include listing channels, setting the default channel, previewing the message layout, updating the format template, and sending an EOD update on demand.

Troubleshooting tips: ensure the bot/user is a member of the target channel, double-check tokens, and restart your IDE if messages fail to post. If you encounter invalid_auth, verify the token type and prefix (xoxb- for bot; xoxp- or xoxs- for user). If you see No channel specified, set the default channel. For VS Code, confirm Copilot is enabled and the MCP server appears in the Copilot Chat tools list.

Available tools

list_channels

List channels your Slack token can read.

set_default_channel

Set the default Slack channel for EOD posts.

preview_format

Preview the layout/format of the EOD message before sending.

update_format_template

Update the message template used for EOD posts.

eod_status

Send an EOD update now; the server builds a summary from your workspace conversations and posts to the chosen channel.

configure slack_token

Save tokens and default channel locally for quicker setup.

Built by

VeilStrat

AI signals for GTM teams