Discord
Linking your Discord account lets Sharick recognize you when you create or receive Sharick todos in Discord. It does not install the bot and does not give Sharick permission to manage the server.
Prerequisites
Section titled “Prerequisites”- A Sharick account.
- Sharick is already installed in the Discord server by an organizer or administrator.
Installing Sharick in a server is a separate, one-time administrator step that requires Discord’s Manage Server permission. Linking your own account does not require that permission.
Connect from Discord
Section titled “Connect from Discord”- In a Discord server where Sharick is installed, enter
/sharick link. - Sharick replies privately. Click Connect to Sharick.
- Sign in to Sharick in the browser if prompted.
- Review the Discord identity request and approve it.
The member connection asks Discord only to identify your account. It does not request bot installation or server-management permissions.
Connect from Sharick Settings
Section titled “Connect from Sharick Settings”If the Discord command is not available, use the settings flow:
- Open Sharick and go to Settings → Integrations → Discord.
- Click Connect my Discord account.
- Complete the Discord approval in your browser.
Do not choose Install Sharick in a server unless you are the server administrator performing the one-time installation.
Verify it worked
Section titled “Verify it worked”Open Settings → Integrations → Discord. The Discord section should show Account linked and your Discord name.
You can also right-click a Discord message, choose Apps, and select Create Sharick todo. Sharick should respond privately with a link to the new todo.
Post through MCP
Section titled “Post through MCP”The MCP tools can list channels, preview or post a message, and remove a bot message sent on your behalf. Your Discord account must be linked, and you must have installed Sharick in the selected server. Posting also checks your account’s View Channel and Send Messages permissions; Discord enforces the bot’s own permissions when it sends.
- Call
sharick_list_discord_channelsand select the exact channel ID. - Find the person in Sharick People. A mention needs exactly one active,
confirmed numeric Discord user ID. Names, inferred matches, and ambiguous
accounts cannot be used. If needed, confirm the exact mapping with the
person using Sharick, then attach it with
sharick_add_person_identity(kind: "discord",confirmedByUser: true). Corrections also require confirmation; existing People tools can remove a mistaken identity. - Call
sharick_send_discord_messagewithchannelId,content, optionalmentionPersonPublicIds, and optionaltodoPublicId. The defaultdryRun: truereturns the prepared content without posting. - After the user authorizes that message and channel, set
dryRun: false. The result includes the Discord message ID and URL. Usesharick_delete_discord_messagewith the channel and message IDs to undo your own recorded bot post.
A todo link comes from the accessible todo record using its public ID; it does not grant recipients access to a private todo. Messages cannot ping roles, everyone, or users outside the verified mention list. DMs and threads are not supported. Never retry an uncertain send automatically: check Discord first to avoid a duplicate. A successful send followed by a local recording failure returns the message URL and a warning; remove that post in Discord if necessary.
First-party MCP keys support these tools through their full-user grant.
Narrow keys need discord:read for channel discovery and discord:write
for sending or deleting, plus people:read for mentions and todo:read for
todo links. Existing OAuth connectors do not silently gain Discord posting
access; these new Discord scopes are not added to the legacy connector grant.
Troubleshooting
Section titled “Troubleshooting”/sharick link does not appear
Section titled “/sharick link does not appear”Confirm that Sharick is installed in that server. Discord application commands can also take a short time to appear after installation or an update. Use the Sharick Settings flow above if you do not want to wait.
Discord asks for Manage Server permission
Section titled “Discord asks for Manage Server permission”You opened the administrator installation flow. Go back and use /sharick link or Connect my Discord account instead.
The browser asks you to sign in
Section titled “The browser asks you to sign in”Sign in to the Sharick account you want to connect, then continue. Sharick requires the browser session so it can connect the Discord identity to the correct Sharick account.
The wrong Discord account is shown
Section titled “The wrong Discord account is shown”Cancel the approval, switch to the intended Discord account in the browser, and try again. Afterward, confirm the Discord name shown in Sharick Settings.
The Discord account is already linked
Section titled “The Discord account is already linked”One Discord identity cannot belong to multiple Sharick accounts. Disconnect it from the other Sharick account or contact [email protected].
For server administrators
Section titled “For server administrators”In Sharick, open Settings → Integrations → Discord and click Install
Sharick in a server. Select the server and approve the requested permissions.
Afterward, each member links their own identity with /sharick link; members
do not reinstall the bot.
Links for automatically created ToDos
Section titled “Links for automatically created ToDos”When a channel is linked to a Topic and Sharick creates a ToDo from a message, it adds 📝 to the source and posts an app-opening link inside that message’s thread. Existing threads are reused; otherwise Sharick starts one named Sharick ToDo. The link opens the ToDo in the mobile or desktop app, with an Open on Web option. On mobile, sign in before following the link; if login was needed, tap the Discord link again afterward.
The bot needs Add Reactions, Create Public Threads, and Send Messages
in Threads, along with access to the source channel and message history.
For an existing installation, grant these permissions or reinstall the bot.
Channel permission overrides still apply. Deployments overriding
DISCORD_INSTALL_PERMISSIONS must include these permissions too.
If a thread reply cannot be sent (for example, the thread is locked or the bot lacks permission), the ToDo remains created. Sharick does not post the link in the parent channel as a fallback; failed replies are not automatically retried.
Status on the source message
Section titled “Status on the source message”Sharick uses 📝 to show that a message has an open todo. Completing the todo replaces 📝 with ✅. If the message was turned into a todo by mistake and needs no action, use Archive in the todo’s menu (or delete the todo); Sharick removes its task markers from the message. Archiving an already completed todo keeps ✅, since the work was done.
Not important lowers priority and can allow the todo to appear again; snoozing postpones it. Both keep 📝 because the todo is still open. Undoing completion or restoring an uncompleted archived todo restores 📝. Restoring archived completed history keeps ✅.
If several people captured the same message, 📝 remains while any copy is still open. Once all copies have been completed or withdrawn, ✅ appears if any work was completed; otherwise Sharick removes its task markers. Other people’s reactions are preserved.
Status synchronization runs in the background and retries temporary Discord failures. A prolonged outage, missing bot permissions, or a server restart can leave the status mark out of date until the next todo status change.