Skip to content

Add resources support to SDK #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 3 commits into from
Oct 20, 2025
Merged

Add resources support to SDK #5

merged 3 commits into from
Oct 20, 2025

Conversation

@peteski22
Copy link
Contributor

@peteski22 peteski22 commented Oct 17, 2025 •
edited
Loading

Summary

Implements resources and resource templates support following the MCP specification (2025-06-18).

Server-Level API

// Direct server access
await client.servers.files.getResources()
await client.servers.files.getResourceTemplates()
await client.servers.files.readResource(uri)
await client.servers.files.hasResource(uri)  // Safe boolean predicate

Key Features

  • Server-level resource operations via dynamic caller
  • Graceful degradation for servers without resource support (501 responses)
  • Automatic health checks before resource operations
  • Support for both text and blob resource content
  • Full TypeScript support with comprehensive type definitions

Implementation Details

  • Follows existing patterns from tools and prompts implementation
  • Uses dynamic caller pattern for clean API ergonomics
  • Health checks ensure operations only run against healthy servers

@peteski22 peteski22 requested a review from khaledosman October 17, 2025 15:28
khaledosman
khaledosman approved these changes Oct 18, 2025
View reviewed changes
@peteski22
Implement full resources and resource templates support
2120363 
  Server-level methods:
  - getResources(), getResourceTemplates(), readResource(uri)
  - hasResource(uri) safe boolean predicate

  Client-level methods:
  - Aggregation across servers with namespacing (serverName__resourceName)
  - Auto-population of resource cache on first readResource() call
  - Filtering by specified servers
  - Graceful handling of 501 Not Implemented and unhealthy servers
@peteski22
Refactor SDK method names (#6)
cab250f 
* (client) getToolSchemas -> getTools
* (server) listTools -> getTools
* Remove console messages
@peteski22
Remove over complex logic from SDK
21636b1
@peteski22 peteski22 force-pushed the peteski22/support-resources branch from b4aaf35 to 21636b1 Compare October 20, 2025 12:37
@peteski22 peteski22 merged commit 3b56aa0 into main Oct 20, 2025
2 checks passed
@peteski22 peteski22 deleted the peteski22/support-resources branch October 20, 2025 12:41
@peteski22 peteski22 added this to the mcpd milestone Oct 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@khaledosman khaledosman khaledosman approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@peteski22 @khaledosman