---
title: "Discussion on \"Building mcp-pool: one week, eleven MCP servers, one shared OAuth library\" | Hashnode"
description: "Discussion on \"Building mcp-pool: one week, eleven MCP servers, one shared OAuth library\". Building mcp-pool: one week, eleven MCP servers, one shared OAuth library\n\nThis is another post in the series where I walk through my open-source projects. Earlier ones covered backupctl, agent-sessions, and a few smaller tools. This one is about mcp..."
url: "https://hashnode.com/posts/building-mcp-pool-one-week-eleven-mcp-servers-one-shared-oauth-library/69e85ce9453de5f39e1b6c8d"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Building mcp-pool: one week, eleven MCP servers, one shared OAuth library](https://vineethnk.hashnode.dev/building-mcp-pool-one-week-eleven-mcp-servers-one-shared-oauth-library?utm_source=hashnode&utm_medium=feed)

Building mcp-pool: one week, eleven MCP servers, one shared OAuth library This is another post in the series where I walk through my open-source projects. Earlier ones covered backupctl, agent-sessions, and a few smaller tools. This one is about mcp...

Apr 22 · 12 min read · vineethnk.hashnode.dev  
Read the article

-   [#ai-tooling](https://hashnode.com/tag/ai-tooling)
-   [#mcp](https://hashnode.com/tag/mcp)
-   [#monorepo](https://hashnode.com/tag/monorepo)
-   [#oauth](https://hashnode.com/tag/oauth)
-   [#typescript](https://hashnode.com/tag/typescript)

## Written by

[Vineeth N K](https://hashnode.com/@vnknotes)

@vnknotes

  
[View profile](https://hashnode.com/@vnknotes)

What I learned the hard way. So you do not have to.

Hi, I am Vineeth (VNK). I am a software developer and DevOps engineer based in Kochi, India. I work across backend (Node.js, NestJS, PHP), infrastructure (Docker, MySQL, Linux), and frontend (Vue, React). I am currently building and operating products with BEO, where I do everything from architecture decisions to staging deployments to fixing the things that break at 9 PM on a Friday. I write about real problems from real work - the kind of things you do not find in tutorials. Production incidents, hard-won architecture lessons, team and process notes, and the occasional opinion piece. If something I shipped, broke, or learned might save someone else half a day, it goes here. No fluff. No ghostwritten thought leadership. Just notes from the terminal.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
