My MCP dashboard just got emptied. I used to be able to see all my MCP configs in [this dashboard](https://mcp.composio.dev/dashboard/servers) and out of nowhere it got emptied. I make use of this dashboard to get the

Streamable HTTP

URL of the MCP for my backend to connect to and now I cannot do this. My usual flow is: 1) Go to the [platform](https://platform.composio.dev/) 2) Create the MCP config (and associated Auth Config) 3) Then go to the dashboard and get the connection URL This is now broken https://cdn.discordapp.com/attachments/1426132737185677483/1426132737437204601/image.png?ex=68ed68dc&is=68ec175c&hm=efe0b507544c78374da3d0d380a33bbf4b1dd8f2d3216c189653464c76873bd6&

Hey, could you please share the support debugging info? You can find it here: https://platform.composio.dev?next_page=/settings

Hey @abhishekpatil4 It's here:

@project_id: nGFL0JpPK_Dx
@org_id: cXGcW99DJLQE
@org_member_email: sebastiao+composio@spinnable.ai
`

thanks, will take a look and get back soon.

Hello @abhishekpatil4 still no MCP configurations available. I can see them in [the platform](https://platform.composio.dev/widn-bob/default/) but none in [the dashboard](https://mcp.composio.dev/dashboard/servers) https://cdn.discordapp.com/attachments/1426132737185677483/1427229531919351858/image.png?ex=68ee1a95&is=68ecc915&hm=59e9a5f27b5f313f90513be393fb33fe2ae23d414501ebcfda67533d1934ce47& https://cdn.discordapp.com/attachments/1426132737185677483/1427229532250837002/image.png?ex=68ee1a95&is=68ecc915&hm=fbf9b489b8ca539a37f4c75a2691a2e6a02b670ffdc1437bf9a9027cb98447d5&

I've escalated this internally, we'll get back in sometime.

Thank you for your help 🙏

Hey, this issue should be solved by logging out and back in.. since its not working in your case we would need some additional info. Mind hopping on a quick call to discuss?

Hey @abhishekpatil4 Building an agentic platform where users can easily create their own agents and connect them to several different tools

Nicee! The fix may take some time as this is happening with very few users & the team is investigating it. In the meantime, would you like me to give you a tour of our platform so you can get unblocked? Also, we recently launched [tool-router](https://docs.composio.dev/changelog) — I'd love to hear your feedback on it!

It would be nice to see how I can get the Streamable HTTP URL for a given MCP configuration yes! It's the main blocker as things stand I haven't had the time to investigate the new

Tool Router

, I am afraid I'm not the best person to provide you with feedback

The URL is

https://apollo.composio.dev/v3/mcp/{{mcp-config-id}}

and to use it for a specific user they should be connected the associated authConfig — once done you can pass the connectedAccId/userId

https://apollo.composio.dev/v3/mcp/{{mcp-config-id}}?user_id={{user-id}}

(can use connected_account_id too). Lmk if you have any other questions

Hey @abhishekpatil4 I was able to connect using the

apollo

URL, however I am having an issue with distinct

auth_config

connections for a given toolkit slug. Is this something you could help me with? I'd be happy to jump on a quick call

Sure, waiting for you here:

Here's the guide: https://docs.composio.dev/changelog/2025/9/15 @sebas_17731 Can you also share the connection ID which has all scopes whereas the authConfig has a subset of it.

Yes, it's this one:

ca_QB2Rfcd5H7p1

Do you want me to prevent deleting it while you debug?

Yes pls

Also, is it possible to, when creating an MCP config to apply an already existing

auth_config

or do I always have to create a new one?

Hey Re the Outlook scopes issue. If you've already granted scopes to a specific OAuth app then try to connect the next time with limited scopes, both previously granted scopes + new limited scopes would be granted. If you're connecting your account to an OAuth app for the first time, in that case if you select certain scopes, then only those would be granted — hope think make sense. If you give access to all tools (both MCP servers) to your agent, then tool choice selection depends upon the agent. And the connection used while calling the tool depends upon the userId which you've passed in the URL as a query parameter. Note that the userId is scoped to the toolkit, so if you have multiple connections with the same userId then the most recent one would be used.

Regarding the first point: I was connecting to it the first time in the call with you, how did the

connected account

get all the scopes (even the ones outside the

auth_config

Regarding the second: Let's say I have: 1)

Outlook-Read-MCP

with the associated auth_config:

outlook-read-config

with tools

A, B and C

2)

Outlook-Send-MCP

with the associated auth_config:

outlook-send-config

with tools

D, E and F

I (

user_a

) connect to the

Outlook-Read-MCP

which creates a

connected account

on

outlook-read-config

. Now, if I try to execute tool D on

Outlook-Send-MCP

, it works and I don't want it to Is it posible to restrict it?

> I was connecting to it the first time in the call with you, how did the connected account get all the scopes (even the ones outside the auth_config Was this account not connected to Composio before? 2nd issue: I would recommend not giving access to certain tools in that case.

1) What do you consider

connected to Composio

? Connected to outlook in Composio? Or connected to any tool in Composio? 2) What do you mean? Not using a tool

A

at all in any of the MCP configs?

1) Let me rephrase it — Was this Outlook account which when connected to Outlook toolkit had all the scopes even when scopes were limited in the authConfig had been previously connected to Outlook toolkit (irrespective of authConfig). 2) Since you're maintaining 2 different MCP configs (ie one with tools that can

write

and other with tools that can just

read

), you can add a condition to not show/give agent access to write tools if user has not connected his account to that mcp config (or the associated authConfig), hope this make sense. Can hop on a quick call if needed.

1) Got what you mean. I believe it is possible yes. In this case, is there a way I can revert this and start over to only allow the wanted scopes?

Yes, you can follow this guide: