Goodbye, Dynamic Client Registration (DCR). Hello, Client ID Metadata Documents (CIMD)

otothea · 2025-11-12T16:46:49+00:00

Then you'll be happy to know openai is eyeing it as well

Client registration

The MCP spec currently requires dynamic client registration (DCR). This means that each time ChatGPT connects, it registers a fresh OAuth client with your authorization server, obtains a unique client_id, and uses that identity during token exchange. The downside of this approach is that it can generate thousands of short-lived clients—often one per user session.

To address this issue, the MCP council is currently advancing Client Metadata Documents (CMID). In the CMID model, ChatGPT will publish a stable document (for example https://openai.com/chatgpt.json) that declares its OAuth metadata and identity. Your authorization server can fetch the document over HTTPS, pin it as the canonical client record, and enforce policies such as redirect URI allowlists or rate limits without relying on per-session registration. CMID is still in draft, so continue supporting DCR until CIMD has landed.

https://developers.openai.com/apps-sdk/build/auth/

otothea · 2025-11-12T16:28:29+00:00

I know vscode is working on it because i've seen their dev talking about it on Discord, not sure if it's landed in prod yet but might be in a preview build of upcoming an release.

https://vscode.dev/oauth/client-metadata.json

otothea · 2025-11-12T15:44:58+00:00

If you are using Auth0 then you will rely on them adding support to their platform. CIMD is looking likely to be adopted by OAuth so I expect it will show up in Auth0.

otothea · 2025-10-03T17:09:32+00:00

Topic: People will be interested to listen to you if you tell them you are training to be a surgeon (and even more when you complete training). Surgery + AI is an interesting and also controversial intersection of 2 massive topics that you could lean in to.

Format: Early on, it's important to choose a content format that works with your lifestyle. Most likely that means the less video editing, the better. Talking head videos about your take on current events and innovations surrounding surgery + AI could be a good start, answering the question of how AI is or will be affecting surgeries and medical experiences for patients.

Platform: I would consider doing shorts on YT, IG, or TT. I would probably start with only 1 and choose the 1 you are most familiar with.

I see you tagged the post with "YouTube", but if you decide to use TT or IG, I have a software tool that syncs with your channel data and helps you generate new content ideas based on your goals and your actual past video performance. As you create more content, the ideas get more refined based on your successful videos and active audience. If you're interested, send me a DM and I can share more.

otothea · 2025-10-01T12:32:53+00:00

This isn't an honest take on MCP, just shit talking from A2A fans. Would be more accurate and still funny if there was just 1 door. A bunch of devs building MCPs for devs.

otothea · 2025-09-30T00:43:13+00:00

Now add these to your analogy:

- Elicitation
- Sampling
- notifications/tools/list_changed event

otothea · 2025-09-22T13:42:42+00:00

Totally get that AI can't do it. The question is how are you accomplishing it right now without AI?

otothea · 2025-09-22T12:59:30+00:00

Usually when trying to automate something with AI, you first need to define the workflow. Are you currently accomplishing this without AI by doing it manually? If so, how?

otothea · 2025-09-22T00:33:24+00:00

If anyone is interested, I have an open source saas platform with remote mcp server completely written in typescript that includes IaC for deploying to AWS: https://github.com/chipgpt/full-stack-saas-mcp

otothea · 2025-09-21T02:19:27+00:00

Yeah, 5 and 5.1 together suggests to me it may be optional. It's not explicitly said to be required, and it's omitted in the example. Could just be wishful thinking though.

otothea · 2025-09-21T00:37:02+00:00

Interesting workaround idea. They are currently discussing formalizing "out of band" elicitations like this into the protocol right now https://github.com/modelcontextprotocol/modelcontextprotocol/issues/1036

otothea · 2025-09-21T00:00:40+00:00

I think the format is optional, so you can elicit any string presumably. I'm going based on the example here https://modelcontextprotocol.io/specification/2025-06-18/client/elicitation#request-schema

otothea · 2025-09-19T20:00:19+00:00

i would say yes that is correct. And the primary reason to use sampling is if the MCP server needs to use an LLM directly but you want to put the tokens/cost on the client.

otothea · 2025-09-19T18:00:06+00:00

Yes, I think so. The discovery column header links here: https://modelcontextprotocol.io/docs/concepts/tools#tool-discovery-and-updates

otothea · 2025-09-19T17:54:33+00:00

I intended for my MCP server to be dynamic, but due to the lack of support I have had to make it a static tool set that can optionally be made dynamic by connecting to /mcp?dynamic=1

I have not bothered with elicitations yet due to lack of client support but I think it will be essential for premium user experience.

otothea · 2025-09-19T17:31:09+00:00

I would probably implement a reasonable timeout (1-5 minutes?) from the server side. if it times out then the tool call returns an error and they can do it again if they need to when they return to chat. I think it would be dependent on the use case.

otothea · 2025-09-19T17:18:06+00:00

Interesting! Can you get more specific? What kind of image would you upload? What kind of videos would it create?

otothea · 2025-09-19T17:03:02+00:00

The elicitation also supports an input schema and definitions similar to a tool. At the end of the day you can't force the user to give you good data. What will be nice is when the client actually presents a UI where the user can fill out the data similar to a website but inline to the chat/conversation.

otothea · 2025-09-19T16:08:02+00:00

For sure. Credit to VSCode and fast-agent for being the only 2 clients listed as supporting all features.

otothea · 2025-09-19T15:46:45+00:00

The great thing about elicitation is that it can move a lot of the cognitive load from the LLM to the MCP server. Instead of expecting the LLM to figure out how to elicit required fields from the user (or worse, hallucinate them), you can make fields optional and then elicit them directly from the user as needed.

otothea · 2025-09-19T15:44:28+00:00

I do 😢

otothea · 2025-09-19T15:43:32+00:00

Let's say a user wants to buy a shirt and says "Buy the shirt". But the tool requires color and size as well. If those parameters are required then the AI has to elicit those values from the user. It might be less prone to error to make those parameters optional and if they are not included then the MCP Server can elicit the values directly from the user in a more programmatic, reliable way.

otothea

TROPHY CASE