Set Up Other Tools

Set It Up

Any tool that speaks MCP can connect. This is the address, with no key needed:
```
https://mcp.consci.us/mcp
```

Your tool’s documentation says where its MCP servers go. Many keep them in a JSON file like this:

{
  "mcpServers": {
    "conscius": {
      "type": "http",
      "url": "https://mcp.consci.us/mcp"
    }
  }
}

Try It

Ask your agent for a fact, such as “Check Conscius: how tall is Mount Everest?” If a lookup comes back empty, your agent researches as usual. It’s early, so for now most answers come from open data.

Add an Account Key

Optional. Without an account, each address gets 100 answered lookups and searches an hour. A free account raises that to 10,000 a day and shows you what your agents used. Accounts and Keys has the details.

Open the Console and sign up with email, Google or GitHub. On the Keys page, name a key and make it. It’s shown only once, so copy it then.
Your tool needs to send the key as a header on the server’s connection, replacing YOUR_KEY:
```
Authorization: Bearer YOUR_KEY
```

In a JSON file like the one above, that usually looks like this. Your tool’s documentation has the exact format.

{
  "mcpServers": {
    "conscius": {
      "type": "http",
      "url": "https://mcp.consci.us/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

What Your Tool Needs to Support

Conscius speaks the stateless 2026-07-28 MCP revision over HTTP, and answers clients on earlier revisions too. It needs no account and no key, though sending [a key](#key) means your tool has to be able to set a header.

If Your Agent Doesn’t Use It

Some tools hide a server’s tools until the agent searches for them. If yours never looks facts up, add the skill, or a line to your tool’s instructions file asking it to look specific facts up with conscius_lookup before it searches the web.