# Toolcape + Discord

Toolcape connects a company’s existing AI to its systems through one MCP entry point, with account connections, group and individual permissions, and audit logs. This documentation describes a product prototype; it is not evidence that a live server or account is connected.

## The connection
Discord: Conversations in servers and channels. A Discord integration works through a clearly identified bot account.
Connection type pending setup
Bot account managed by an administrator. Messages are sent as the bot, and its channel permissions determine access.
Status: proposed, requires implementation and verification.

## Typical actions
- Read: Read conversations in channels the bot may access
- Create: Post replies and updates as the bot
- Read: Receive direct messages sent to the bot
Planned connection. The bot acts as itself, not as your private Discord account. Discord prohibits self-bots that automate normal user accounts outside the approved OAuth2/bot API. The bot cannot read your unrelated private conversations. Channel permissions and message-content requirements determine what it can read.
Discord bot account policy: https://support.discord.com/hc/en-us/articles/115002192352-Automated-User-Accounts-Self-Bots
Channel permissions: https://docs.discord.com/developers/topics/permissions
Message content and intents: https://docs.discord.com/developers/events/gateway#message-content-intent

## Setup
1. Create a Discord application with a bot account. An administrator installs it on the relevant server.
2. Allow only the required channels and actions, such as viewing a channel, reading history and sending messages.
3. Decide which events and message content the bot needs. Some content access requires Message Content Intent and, where applicable, Discord approval.
4. Configure the bot API or approved MCP adapter in Toolcape. Store the bot token in the credential store, never in an AI prompt.
5. Grant Toolcape permissions and test in one channel. Check that messages are attributed to the bot and blocked channels stay inaccessible.

## Permissions
For personal delegated access, the provider account, approved app scopes and Toolcape rules must all permit the action. Shared accounts and application permissions may have other limits. Toolcape combines Everyone and group grants; a personal exception replaces inherited access for that service. Reading can disclose confidential information. Sharing, sending and deletion need separate consideration.

## Calling an operation
First discover which tools the connected Toolcape server actually exposes. If it offers search → describe → execute, find the relevant operation, inspect its input schema and permissions, then call it with validated inputs. Tool names vary by server; do not invent names, arguments, URLs or successful outcomes. Without connected tools, give setup guidance instead of claiming to perform actions.

## Operation reference
Catalog snapshot: 16 September 2026. Verify the current schema before calling.
- read — Read conversations in channels the bot may access
  MCP 
  
- create — Post replies and updates as the bot
  MCP 
  
- read — Receive direct messages sent to the bot
  MCP 
  

## A useful first question
Summarize questions from the support channel.

## If it fails
Check the account, expired authorization, app approval, provider scopes and Toolcape permissions. Share only redacted errors with support. Never paste passwords, tokens or client secrets into an AI conversation.