You can use one of the two MCP Server remote endpoint:
- Streamable HTTP(Recommended): http://127.0.0.1::8089/mcp
- SSE: http://127.0.0.1::8089/sse


And then in MCP client config, set the url to the SSE endpoint:

`js
{
"mcpServers": {
"filesystem": {
"url": "http://127.0.0.1::8089/sse"
}
}
}
`

url to the Streamable HTTP:

`js
{
"mcpServers": {
"filesystem": {
"type": "streamable-http", // If there is MCP Client support
"url": "http://127.0.0.1::8089/mcp"
}
}
}
`

#### In-memory call

If your MCP Client is developed based on JavaScript / TypeScript, you can directly use in-process calls to avoid requiring your users to install the command-line interface to use Filesystem MCP.

`js
import { Client } from '@modelcontextprotocol/sdk/client/index.js';
import { InMemoryTransport } from '@modelcontextprotocol/sdk/inMemory.js';

// type: module project usage
import { createServer } from '@agent-infra/mcp-server-filesystem';
// commonjs project usage
// const { createServer } = await import('@agent-infra/mcp-server-filesystem')

const client = new Client(
{
name: 'test filesystem client',
version: '1.0',
},
{
capabilities: {},
},
);

const server = createServer();
const [clientTransport, serverTransport] = InMemoryTransport.createLinkedPair();

await Promise.all([
client.connect(clientTransport),
server.connect(serverTransport),
]);

// list tools
const result = await client.listTools();
console.log(result);

// call tool
const toolResult = await client.callTool({
name: 'list_directory',
arguments: {
path: '~/your_computer'
},
});
console.log(toolResult);
`

$3

Access http://127.0.0.1:6274/:

`bash
npm run dev
``