Connections
Connect X, Telegram, Slack, and other tools so your agent can post, chat, and pull context from where you work.
Connections give your agent reach beyond your Paragraph site. Some let it publish and read on social channels, some let you chat with it from other apps, and some give it access to the tools your work already lives in.
All of them are managed in Settings → Agent in your workspace.
X
Connect an X account and your agent can post and read on X: publishing threads, checking how they perform, and folding results back into what it writes next.
A few things to know:
- The connected account is the one your agent uses when working on this publication.
- It's shared with everyone on your team, so the whole team's agent work posts from the same account.
- Connecting X requires the Starter plan or above. See Plans and credits.
Once connected, X becomes a distribution channel. A suggestion to post on X is a one-time choice. An enabled X automation is scoped to the named job, trigger and timing, and account you confirm. See approvals.
Telegram
Connect Telegram and message your agent right from your phone. It replies in the chat, and your conversation stays linked to the same session on Paragraph.
That means no context is lost between surfaces. Start a thread from the couch, and pick it up in your workspace later with the full history intact. It's the same agent, same memory, same voice settings.
Slack
Add your agent to your team's Slack. Mention it in a channel or thread and it replies inline, with everything saved back to your Paragraph session.
This works well for teams: anyone in the channel can see the exchange, and the conversation still lands in your Paragraph session history.
Your agent acts as the publication you connected Slack from, so if you write for more than one, open Settings → Agent on the one you want before you connect. A Slack workspace can be connected to one publication at a time.
Tools via MCP
MCP (Model Context Protocol) is an open standard for connecting AI agents to outside tools. Connect a service over MCP, and your agent can use it directly in chat and in tasks.
Select Search providers to browse more than 1,000 compatible remote MCP servers cataloged by integrations.sh. The directory supports OAuth, bearer tokens, and servers that don't require authentication. Popular examples include:
| Provider | What your agent gets |
|---|---|
| Slack | Channels, messages, and workspace search |
| Linear | Issues, projects, and comments |
| Notion | Pages, databases, and workspace search |
| GitHub | Repositories, issues, and pull requests |
| Canva | Designs, brand assets, and creative workflows |
| HubSpot | CRM records, contacts, companies, and sales activity |
| monday.com | Boards, items, projects, and team workflows |
| Sentry | Errors, releases, projects, and application performance |
| Fathom | Meeting recordings, transcripts, summaries, and action items |
| PayPal | Payment operations and developer tools |
With these connected, you can ask things like "summarize this week's Linear issues into a changelog post" or "pull the outline from my Notion page and draft the essay".
The Slack MCP provider is different from the Slack chat connection above. The chat connection lets you talk to your agent in Slack; the MCP provider lets your agent read your Slack workspace as a tool.
Connected tools in automations
Everything you connect is available to your automations too, not just to chat. An automation that drafts a weekly changelog can read your commits on its own, on schedule.
Two rules keep that safe:
- Reading runs on its own. Anything that only reads is available to every automation from the moment you connect it.
- Changes need your say-so. A tool that writes somewhere (filing an issue, posting a message) stays off until you turn it on for that specific automation, in its access settings.
You can also keep a connection out of a single automation. Open the automation, find Connected tools, and switch off the ones it shouldn't reach. It's per automation, so turning one off doesn't affect your other automations or your chat.
Automations only ever see the tools you enabled for that server in Settings → Agent. Turning a tool off there removes it everywhere at once.
Custom MCP servers
Beyond the provider directory, you can connect any remote MCP server. Paragraph supports three ways to authenticate:
- OAuth, for servers that support a standard sign-in flow
- Bearer token, for servers that use an API key
- No auth, for open servers
Bearer-token providers ask for a token before connecting. Paragraph encrypts the token and stores it with that MCP connection.
Add a custom server in Settings → Agent with the server's URL and the auth method it expects. If you're building your own tools, see MCP for developers.
Getting started
Open Settings → Agent at app.paragraph.com.
Select Search providers, choose a service, and follow its sign-in flow. For another service, add its remote MCP URL manually.
Test it in chat: ask the agent to use the new connection, and confirm it responds the way you expect.
Having trouble with a connection? Write to support@paragraph.com and we'll help you sort it out.