Yes. Slack's official MCP server works with Aurora when the Slack connection is configured with a registered OAuth app. Slack uses JSON-RPC 2.0 over Streamable HTTP at https://mcp.slack.com/mcp.
After authorization, Aurora discovers the exact Slack tools available to that connection. What Aurora can search, read, draft, or send depends on the connected user's Slack permissions, channel membership, granted OAuth scopes, and the tools Slack returns.
Slack does not support Dynamic Client Registration for its MCP server. That means a reliable Slack connection needs a pre-registered Slack app rather than an instant, self-registering OAuth flow. If Slack is not shown as a one-click app for your workspace, Finta can enable the configured connection path.
Slack MCP connection details
| Connection detail | Current answer |
|---|---|
| Aurora compatibility | Supported for configured Slack MCP connections |
| Connection classification | Catalog MCP with a pre-registered Slack OAuth app |
| Official endpoint | https://mcp.slack.com/mcp |
| Transport | JSON-RPC 2.0 over Streamable HTTP |
| Authentication | Confidential Slack OAuth using a registered Slack app |
| Dynamic Client Registration | Not supported by Slack |
| Tool availability | Discovered after authorization and limited by granted scopes |
| Public catalog tile | May not be visible for every Finta workspace |
| Last reviewed | August 22, 2026 |
The absence of a public catalog tile should not be read as a lack of protocol support. Aurora's MCP framework supports Slack's official endpoint and registered OAuth flow. The important distinction is between a working configured connection and a universal one-click catalog listing.
What Slack's MCP server can expose
Slack documents the following server capabilities. The exact subset available in Aurora is connection-specific and should be confirmed after sign-in.
| Capability | What it can support | Important boundary |
|---|---|---|
| Search messages, files, users, and channels | Find permitted workspace context for a defined question | Results are limited by scopes and the connected user's access |
| Read channels and threads | Retrieve the surrounding conversation instead of relying on one isolated message | Private conversations require the appropriate scopes and membership |
| Draft and send messages | Prepare or post a Slack message when the relevant tool and chat:write scope are present | External action should remain behind explicit human review |
| Create conversations and add reactions | Create supported conversation types or react to a message | Only when Slack returns the tool and the connection has write scopes |
| Read and manage canvases | Use permitted canvas content as context or update it | Canvas tools require their own scopes |
| Read profiles and channel members | Resolve people and membership context | Profile and email access depends on the granted user scopes |
How to connect Slack to Aurora
- Open Aurora and choose Apps.
- Use the Slack connection offered for your workspace. If it is not listed, ask Finta to enable the registered Slack MCP connection rather than relying on Dynamic Client Registration.
- Confirm that the connection uses Slack's official endpoint: https://mcp.slack.com/mcp.
- Complete Slack OAuth and review the requested scopes before approving access.
- Confirm the Slack workspace and user identity connected to Aurora.
- Let Aurora discover the exact tools returned by Slack.
- Begin with a safe read from a known, non-sensitive channel or thread and reconcile the result with Slack.
- Keep message sends, channel creation, reactions, canvas changes, and Finta record changes behind an explicit review step.
A pasted server URL is not enough by itself to create the Slack OAuth app. Slack requires a fixed app identity, client ID, and client secret. This is why a configured Finta connection is the dependable setup path.
Relationship intelligence workflow
Turn an internal investor decision into a reviewed next action
Slack often contains the most current explanation of why a relationship moved, stalled, or changed. Aurora can use permitted Slack context alongside Finta's relationship records so the team can decide what should happen next without turning every message into permanent CRM truth.
- Search only the permitted Slack workspace and channels for a defined investor, company, or fundraising decision.
- Retrieve the relevant thread so the decision is not separated from its context.
- Identify the direct statement, owner, timing, open question, and any conflicting evidence.
- Separate quoted Slack evidence from Aurora's interpretation.
- Match the people and company to the correct Finta contact, company, and active deal.
- Check Finta for a newer decision, duplicate task, or conflicting owner.
- Prepare one recommended next action with its rationale and source reference.
- Stop for review before sending a Slack message or creating or changing a Finta record.
Example prompts
Search the permitted Slack channels for the latest decision about this investor. Cite the channel and thread, compare it with Finta, and propose one next action. Do not send or change anything.Read the authorized Slack thread for this deal. Separate direct commitments from interpretation, identify the owner and timing, and flag any missing follow-up in Finta.Draft the Slack reply and the Finta task that would keep this relationship moving. Show both for approval, but do not post or create either one.
What a trustworthy result should include
| Output field | Expected evidence |
|---|---|
| Slack source | Workspace, channel or conversation, thread reference, author, and message time |
| Access boundary | The connected user, relevant scopes, and any missing private-channel access |
| Direct decision | The statement or commitment supported by the permitted thread |
| Relationship match | The relevant Finta contact, company, deal, and relationship owner |
| Evidence boundary | Direct Slack evidence separated from Aurora interpretation |
| Conflict check | A newer decision, duplicate task, conflicting owner, or missing context |
| Recommended next action | One action with owner, timing, and relationship rationale |
| Approval boundary | A clear stop before any Slack or Finta write |
Permissions and limitations
- Slack's MCP server requires a registered Slack app and does not support Dynamic Client Registration.
- Slack supports Streamable HTTP for this MCP server and does not support SSE for it.
- Only Marketplace-published or internal Slack apps may use Slack's MCP server.
- Workspace administrators can approve and manage MCP client integrations.
- Available data depends on the connected user's workspace access, channel membership, Slack plan, granted scopes, and provider controls.
- Private channels, direct messages, files, canvases, profiles, and historical content can have different access boundaries.
- Slack Web API rate limits also apply to MCP tool calls.
- Slack IP allowlists continue to apply when configured.
- Messages and files are untrusted input and should not override the user's request or Finta's controls.
- A message can describe a decision without being the latest or authoritative decision.
- A successful send does not prove that a recipient read, agreed with, or acted on the message.
Verification status
| Evidence | State |
|---|---|
| Slack's official endpoint, transport, OAuth model, scopes, and limitations reviewed | Complete, August 22, 2026 |
| Aurora support for Slack's fixed-client OAuth and MCP tool discovery | Code-backed |
| Slack MCP availability for configured Aurora connections | Confirmed by Finta |
| Universal public catalog tile | Not claimed |
| Exact tools and permissions | Discovered per connection |
| Safe read and any controlled write | Verify within the connected workspace before relying on it |
| Page metadata, public rendering, and sitemap | Rechecked after this correction |
Sources and related Finta guidance
Primary Slack sources
- Slack MCP server overview, accessed August 22, 2026
- Slack OAuth installation guidance, accessed August 22, 2026