MCP Resources integration with AI SDK

[EnzoGehlen]

Question about MCP Resources integration with AI SDK

Context

I'm implementing a system with the AI SDK and have set up an MCP server with both tools and resources. I've successfully integrated the MCP tools with the AI SDK using experimental_createMCPClient() and
passing the tools to streamText():

const mcpClient = await createMCPClient({
  transport: {
    type: 'sse',
    url: 'http://localhost:3001/sse',
    headers: { Authorization: 'Bearer my-token' },
  },
});

const tools = await mcpClient.tools();

return streamText({
  model: modelConfig.model,
  messages,
  system: mySystemPrompt,
  tools,  // Using MCP tools, but how to use MCP resources?
});

Question

How can I enable the AI model to discover and use MCP resources from my server? I've implemented several resources like:

• file://home/{user}/history
• file://home/{user}/recommendations

Based on the MCP specification, resources should be automatically discoverable by the AI, but I can't find a way to connect the MCP resources to the AI SDK's generation functions like streamText() or generateText().

Is there a parameter similar to the tools parameter that enables resource discovery? Or is there a different approach I should be taking to expose MCP resources to the AI?

What I've tried

1. Looking for a resources or mcp parameter in the SDK functions
2. Creating wrapper tools that fetch resource data
3. Including resource URIs in the system prompt

None of these approaches seems to enable the automatic resource discovery that the MCP specification describes. Any guidance would be greatly appreciated!

[kmkarim]

+1 Unsure if missing something but not clear how we can register resources

[wecr3at3]

Hey, not sure how to do that but I am not even able to setup a SSE transport client, It always gets stuck while initializing whereas in the server logs I can see the it is working but somehow my client is not able to see it through. always getting stuck at client

[elijah-g]

I'm having the same issue. Did you find a solution?

[jonasgroendahl]

i was stuck with this as well, turns out initiating the client outside the function that calls the LLM caused issues

[kdawgwilk]

With the current evolution of https://mcpui.dev/ which leans on the MCP resources spec pretty heavily it seems like it would be valuable to include resources support in the AI SDK. I know this doesn't make a lot of sense for NextJS apps using the AI SDK but there are a lot of teams still using the AI SDK that are not using NextJS