MCP Server overhaul - connecting every MCP to the main datapoint #10
Labels
No labels
needs/docs
needs/research
needs/upstream
type/bug
type/external
type/feature
type/refactor
urgency
high
urgency
immediate
urgency
low
urgency
medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ScottyLabs/mcp-server#10
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every MCP right now talks to a service - CMU Courses, CMU Maps, CMU Eats. But, this is kind of inefficient. What if we directly communicated at the data source instead of having an intermediary service (in this case, ScottyLabs).
Investigate into this issue. This would take a long while and would require multiple PRs.
For each service, I would like to have 4 people working on it.
Timeline: TBD (based on initial investigations).