Connection guide for the Chemia materials MCP connector
Add the server URL to a client that supports remote MCP servers, sign in with an approved Elixir account, and approve read access. We list a client below only after we have run it against the connector and recorded the date. We make no claim about any other client.
| Server URL | https://mcp.chemiadiscovery.com/mcp (the /mcp path is part of the address) |
|---|---|
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with an Elixir account |
| Access requested | materials:read, read access to materials data |
| Account needed | An Elixir account that an administrator has approved (how access works) |
| Clients tested | 1, listed below |
| Data as of | 2026-10-04 |
| Server release | 1.5.0, read from the live server on 2026-10-04 |
Which clients have we tested?
We list a client only after we have run it against the connector and recorded the date. As of 2026-10-04:
| Client | How it was connected | Tested on | What we checked |
|---|---|---|---|
| Claude Code | Custom connector added to a Claude account, then used from Claude Code | 2026-10-04 | The connector listed its tools after sign-in. A call to list_material_sources returned the dataset list. |
We make no claim about a client that is not in this table.
What do I need before I connect?
- An Elixir account that an administrator has approved. Without one, the sign-in cannot complete. See Access, grants and limits.
- A client that can add a remote MCP server by URL and complete an OAuth 2.1 sign-in in a browser.
- The full server URL,
https://mcp.chemiadiscovery.com/mcp. The/mcppath is part of the address: the bare host name serves nothing. See Troubleshooting.
How do I add the connector?
- In your client, add a custom or remote MCP server. Some clients call it a connector.
- Paste the server URL:
https://mcp.chemiadiscovery.com/mcp. - When your browser opens, sign in with your approved Elixir account.
- Review the access request (
materials:read, read access) and approve it. - Return to the client. It lists the tools your account is entitled to.
Menu names differ between clients and change between versions, so we give no click paths. Every client that supports remote servers asks for the same two things: the URL, and a sign-in in the browser.
How do I check that it works?
Ask the assistant to list the material datasets, or call list_material_sources directly. It is open to every signed-in account and is not charged, so it works before your account holds any grant and does not use your daily allowance. A list of datasets, each with an id and a description, means the connection and the sign-in both work.
What if something goes wrong?
Troubleshooting covers a browser error on the connector URL, a tool you cannot see, a new grant that has not appeared, and the daily limit.