MCP Tools Not Listed: Why tools/list Is Empty

If the Corcava connection appears active but the client advertises no tools, troubleshoot connector enablement, authorization, and configuration loading in that order. Do not confuse an empty MCP tool list with a working Corcava tool that returns no projects or tasks.

First: identify what is empty

These are different situations:

• No Corcava tools are available: the MCP client did not discover Corcava's tool definitions. Continue with this guide.
• Corcava tools are listed, but “List my projects” returns no records: tool discovery works. Check whether you connected the intended Corcava workspace and whether it contains data.
• Tools are listed, but a call returns 401 or 403: use the 401 guide or 403 guide.

Step 1: enable Corcava in the current client context

Many AI clients let you configure a connector globally but enable its tools separately for a conversation, project, or workspace.

1. Open the current conversation's tools or connectors menu.
2. Confirm that Corcava is enabled.
3. Start a new conversation after enabling it.
4. Ask the client to list the Corcava tools available in that conversation.

If another MCP server's tools appear but Corcava's do not, verify that you selected Corcava rather than a similarly named connection.

Step 2: reconnect an OAuth connector

Use this path if the client asked for a server URL and opened browser authorization.

1. Disconnect your Corcava authorization without removing an organization-managed connector definition.
2. Select Connect on the existing Corcava connector for this server:

https://app.corcava.com/mcp

3. Complete authorization in the browser.
4. Confirm that you are signed into the intended Corcava workspace.
5. Return to the client and enable Corcava in a new conversation.

If the connector definition is missing or its URL is wrong, add or correct it only if you manage connectors for that client. In Claude, individual Pro and Max users can manage their own custom connector; on Team and Enterprise plans, an Owner or Primary Owner manages the organization connector and members reconnect only their own authorization.

If authorization was revoked or expired, reconnecting is safer than trying to repair it with a static API key.

Step 3: check a manual API-key configuration

Use this path only when the client loads Corcava from a JSON or other static configuration file.

Confirm that the entry contains:

{
  "mcpServers": {
    "corcava": {
      "url": "https://app.corcava.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Then check:

• The file is in the location used by this installation of the client.
• The JSON parses successfully.
• YOUR_API_KEY was replaced locally with an active Corcava key.
• The key was created in the workspace you intend to use.
• The client supports the configuration shape you supplied.
• There is only one top-level mcpServers object.

Use MCP Config JSON Errors for safe local validation.

Step 4: reload discovery

After changing a connector or static configuration:

1. Save the configuration.
2. Fully quit or reload the client according to its MCP setup instructions.
3. Reopen it and wait for the connection status to settle.
4. Enable Corcava in a new conversation.
5. Check the available tools again.

Do not start by deleting undocumented application cache directories. That can remove unrelated client state without repairing the connector.

Step 5: verify with a Corcava request

Try these prompts:

• “List the Corcava tools available in this conversation.”
• “Show my Corcava projects.”
• “List my Corcava tasks.”

When discovery succeeds, the client should expose Corcava tools for projects, tasks, boards, comments, and time tracking. The exact presentation and tool-selection interface varies by client.

A browser visit or bare curl GET to /mcp is not a complete discovery test. MCP initialization and tools/list are protocol requests; verify them through the client instead.

Result-based next steps

• Tools now appear and return data: the connection is working.
• Tools appear but no projects or tasks are returned: verify the Corcava workspace and its data.
• The connector returns 401: reconnect OAuth or replace the static key with the 401 guide.
• A tool returns 403: confirm workspace and resource access with the 403 guide.
• The server itself disappears: use Claude Desktop: Server Not Showing.
• The client reports a transport error: use Connection Failed.

For supported clients and both connection methods, see AI Assistant Integration (MCP).