Skip to content

Conversation

@DavidParks8
Copy link
Contributor

Motivation and Context

We need the ability to implement different transports (such as via orleans), without requiring consumers to use methods other than MapMcp.

Breaking Changes

No

Types of changes

  • New feature (non-breaking change which adds functionality)

?? throw new InvalidOperationException(
"You must call WithHttpTransport(). Unable to find required services. Call builder.Services.AddMcpServer().WithHttpTransport() in application startup code."
);
return configurator.Configure(endpoints, pattern);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we should add a hook for a service to replace the implementation of MapMcp() entirely. If you want something that behaves radically differently, you can create your own MapWhateverMcp() method.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It isn't radically different though, It is nearly exactly the same, minus the stateless behavior. Do we really want to force people to have to learn about MapWhateverMcp calls? I can guarantee you that some people will forget to change to the other MapWhatever call and will file an issue about "MapMcp" isn't working

@halter73
Copy link
Contributor

I'm closing this for now. You know how to reach me if you want to discuss or reopen. 😆

@halter73 halter73 closed this Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants