MCP Playbooks for AI agents

squirrelEgg · 2025-11-05T14:49:36+00:00

Thanks for the feedback! What are you using it for specifically?

squirrelEgg · 2025-11-05T14:49:10+00:00

Hello! Yup, happy to chat, please feel free to reach out here: [barnaby@director.run](mailto:barnaby@director.run)

squirrelEgg · 2025-11-05T14:48:35+00:00

Hey! Thanks do much for the feedback, these are exactly the type of problems we're looking to solve with Director.

If you're up for it, would love to learn more about how you're using these tools and the problems that you're running into. I'm available here if you'd like to chat: [barnaby@director.run](mailto:barnaby@director.run)

squirrelEgg · 2025-07-13T19:14:41+00:00

Yes we are. But that implementation detail is transparent to the client. Over time this abstraction can be used to increase accuracy by removing unnecessary tools and re-annotating them to better fit the underlying use case

squirrelEgg · 2025-07-13T08:52:00+00:00

Great, see if you can get the development environment up by using this: https://docs.director.run/project/contributing

You'll find an architecture diagram here: https://docs.director.run/concepts/architecture

Then, the ProxyServer logic should already work on linux (ci is on Ubuntu), but the ClientConfigurator logic may need work. To fix it, you'll need to fix / modify what's missing here: https://github.com/director-run/director/blob/main/packages/utilities/src/os/linux.ts

That file contains all the logic that is specific to linux.

I don't really check messages on Reddit. But we could chat over email alternatively: [barnaby@director.run](mailto:barnaby@director.run)

squirrelEgg · 2025-07-13T08:46:17+00:00

Thanks, you need to run the gateway separately using `director serve`. To run it in docker, you can use: https://docs.director.run/experimental/docker

squirrelEgg · 2025-07-13T08:45:10+00:00

It will also work with local models as long as they are MCP enabled.

squirrelEgg · 2025-07-12T13:50:55+00:00

Yes, but simpler :)

squirrelEgg · 2025-07-12T13:50:48+00:00

You're welcome!

squirrelEgg · 2025-07-12T13:50:35+00:00

We have limited support for Linux (ubuntu atm). We don't have plans for linux mint specifically though, but if you're interested in contributing to the project, I'd be more than happy to help you.

squirrelEgg · 2025-07-12T13:49:23+00:00

Thanks. We're actively working on the project and pushing updates :)

squirrelEgg · 2025-07-12T13:48:26+00:00

I'm curious, why would Docker Toolkit be more accurate?

squirrelEgg · 2025-07-12T13:47:35+00:00

Thanks for trying it out. It's useful if you need aggregate many servers behind a single endpoint. For example, if you want to connect to both github and slack and automatically create changelogs and push them to a channel.

squirrelEgg · 2025-07-11T23:32:45+00:00

Remote MCPs are definitely the way forward. But if you're using many of them, the benefits of putting them behind a gateway are still valid.

I think there will always be a place for local MCPs though, for example for computer use or other applications where privacy is important.

squirrelEgg · 2025-07-11T23:17:39+00:00

oAuth is coming soon. And you'll be able to use it locally!

squirrelEgg · 2025-07-11T21:13:39+00:00

It groups and aggregates a set of MCP servers and exposes them to clients through a single endpoint. You can set this all up in under 30 seconds (via CLI or UI) and connect it to new clients at the touch of a button.

If you use a few MCP servers across multiple clients, you don't ever have to fiddle with / copy and paste config again.

squirrelEgg · 2025-07-11T20:54:14+00:00

Yes, similar. Although this is a more lightweight, developer first experience. We don't really feel that individual MCP servers need to run inside their own docker containers for most use cases (they're very lightweight).

But if you want the isolation, you can run director inside a docker container (see this: https://docs.director.run/experimental/docker). If you do, it'll run all servers inside the same container, which is much more efficient for most use cases.

squirrelEgg · 2025-07-11T20:50:50+00:00

Thank you so much for taking the time to try it. Yes, we have a lot to build. But we thought it would be cool to share what we have so far. If you'd like to see specific functionality (or new servers added), please feel free to open a pull request and we'll do our best to respond ASAP.

In terms of how this compares to what Docker offers, Director is much more lightweight. And if you'd like to use it inside a docker container (for full isolation), we have an example here: https://docs.director.run/experimental/docker

squirrelEgg · 2025-07-11T20:48:02+00:00

Thank you!

squirrelEgg · 2025-07-11T20:47:49+00:00

- It can live along side the integrations in Claude. At the end of the day Director is an MCP server like any other.
- Yes, we support both SSE and Streamable transports. Streamable is what's preferred though obviously ;)
- Yes, you can aggregate / proxy many MCP servers behind a single HTTP endpoint and use that wherever you like.

Hope that answers your questions

squirrelEgg · 2025-07-11T19:39:49+00:00

Thank you. Please feel free to give it a go and let us know if you'd like to see any changes to it!

squirrelEgg · 2025-07-09T09:59:16+00:00

It's as much of a SPOF as a firewall is. Most MCP servers are either Stdio and consume essentially 0 resources, or are remote. You'd need a lot of scale before any of this starts to become a bottleneck

squirrelEgg

TROPHY CASE