3. **2022 in Review (December 29, 2022)**: A personal and professional recap of the year 2022. The author reflects on the highs and lows of the year, emphasizing professional achievements.

4. **Writing a Window Manager in Rust - Part 1 (December 28, 2022)**: The first part of the series on building a window manager in Rust. The author discusses setting up a Linux machine and the challenges of working with X11 and Rust.

5. **Add docker/docker to your dependencies (May 10, 2020)**: A guide for Go developers on how to use the Docker client library in their projects. The post includes a code snippet demonstrating the integration.

6. **First (October 11, 2019)**: The inaugural post on the blog, featuring a simple "Hello World" program in Go.
```

## What’s next?

Now that you’ve learned how to use MCP servers with Gordon, here are a few ways
you can get started:

- Experiment: Try integrating one or more of the tested MCP servers into your
  `gordon-mcp.yml` file and explore their capabilities.
- Explore the ecosystem: Check out the [reference implementations on
   GitHub](https://github.com/modelcontextprotocol/servers/) or browse the
   [Docker Hub MCP namespace](https://hub.docker.com/u/mcp) for additional
   servers that might suit your needs.
- Build your own: If none of the existing servers meet your needs, or you’re
   curious about exploring how they work in more detail, consider developing a
   custom MCP server. Use the [MCP
   specification](https://www.anthropic.com/news/model-context-protocol) as a
   guide.
- Share your feedback: If you discover new servers that work well with Gordon
   or encounter issues with existing ones, [share your findings to help improve
   the ecosystem](https://docker.qualtrics.com/jfe/form/SV_9tT3kdgXfAa6cWa).

With MCP support, Gordon offers powerful extensibility and flexibility to meet
your specific use cases whether you’re adding temporal awareness, file
management, or internet access.

### Compatible MCP servers

These are MCP servers that have been tested with Gordon and are known to be
working:

- `mcp/time`
- `mcp/fetch`
- `mcp/filesystem`
- `mcp/postgres`
- `mcp/git`
- `mcp/sqlite`
- `mcp/github`

### Untested (should work with appropriate API tokens)

These are MCP servers that were not tested but should work if given the
appropriate API tokens:

- `mcp/brave-search`
- `mcp/gdrive`
- `mcp/slack`
- `mcp/google-maps`
- `mcp/gitlab`
- `mcp/everything`
- `mcp/aws-kb-retrieval-server`
- `mcp/sentry`

### Unsupported

These are MCP servers that are currently known to be unsupported:

- `mcp/sequentialthinking` - (The tool description is too long)
- `mcp/puppeteer` - Puppeteer sends back images and Gordon doesn’t know how to
  handle them, it only handles text responses from tools
- `mcp/everart` - Everart sends back images and Gordon doesn’t know how to
  handle them, it only handles text responses from tools
- `mcp/memory` - There is no way to configure the server to use a custom path
  for its knowledge base