Integration

Connect Slack to CROssBAR

When New Mention (instant) fires in Slack, your agent runs List drugs in CROssBAR. Describe the whole flow and it is built, tested on every scenario and kept running.

What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.

Build solutions, not workarounds.

What do you want Slack and CROssBAR to do together?

Ask the assistant

You'll sign in before anything runs. What you typed comes with you.

Examples

Pick one to fill the box, then change anything: the steps, the wording, even the apps. Go as long as you like.

Connect your AI client

Give your AI client this address.

https://mcp.apiant.ai

Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.

Set it up in your client
Claude Code

Run this in the directory you want to work in.

claude mcp add --transport http -s project apiant-ai https://mcp.apiant.ai

Start Claude Code there, approve the server, and sign in in the browser page it opens.

Claude Code guide (opens in a new tab)
Claude, web and desktop

Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.

Setup guide (opens in a new tab)
Cursor

Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.

Setup guide (opens in a new tab)
Zed

Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.

Setup guide (opens in a new tab)
Codex and the ChatGPT desktop app

Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.

Setup guide (opens in a new tab)
Any other MCP client

Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.

Setup guide (opens in a new tab)

CROssBAR holds proteins, drugs, molecules, targets, assays and disease and phenotype records drawn from sources like UniProt, ChEMBL, Drugbank, EFO and HPO. Joining it to Slack means a name dropped in a channel, a pinned item or a reaction can pull the matching records out of CROssBAR and put them back in the conversation where the team is already working.

Example flows

What Slack can start in CROssBAR

Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.

Everything your agent can do with Slack and CROssBAR

Triggers and actions 15 triggers · 71 actions

Each app on its own

Reviews

What our customers say

More from Slack

More into CROssBAR

Questions

Slack and CROssBAR, answered

Can something happening in CROssBAR start a workflow in Slack?

No, CROssBAR has no triggers, so every workflow begins with a Slack event such as a new message, a mention, a pinned item or a reaction. CROssBAR is used for the lookups: proteins, drugs, molecules, targets, assays, PubChem compounds and substances, EFO diseases and HPO phenotypes.

Where do the CROssBAR results end up?

Anywhere Slack can put them: a channel message, a thread, a direct message or an ephemeral message seen by one person, and the agent can also pin or react to the original message. You describe what you want and the agent builds it, then tests every scenario before it goes live.

What can start an automation from Slack?

Any of Slack's 15 triggers in the catalog, including New Mention (instant), New Message Posted to Channel, New Pinned Item and New Reaction Added. Describe the moment in plain language and your agent picks the right one.

What can your agent do in CROssBAR when something happens in Slack?

Any of CROssBAR's 11 actions, including List drugs, List EFO diseases, List proteins and List PubChem compounds. Your agent maps the data both ways and tests every scenario before it ships.

Can it also run from CROssBAR to Slack?

CROssBAR has no triggers in the catalog today, so automations start in Slack. If you need the other direction, ask: your agent reads CROssBAR's API documentation and adds it.

Do I have to build a connector for Slack or CROssBAR?

No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.

What happens when something fails?

Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.

Is there a free plan?

Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.