Call for Volunteer Maintainer: Meshery MCP Server Extension

[Lee Calcote]

We are looking for one or more serious, experienced, and self-directed contributors to build a new official Meshery Extension: the Meshery MCP Server.

Project Focus

This extension will provide a dedicated MCP Server that streamlines and accelerates the creation of Meshery designs.

Requirements

• You must be capable of independently defining, architecting, implementing, testing, and fully delivering the project from 0% to 100%.
• The completed extension must include:
  • Full functionality
  • Comprehensive tests
  • Basic documentation
  • Publication / socialization into relevant MCP and Skills marketplaces

Project Details

• The repository will be created under the official organization: https://github.com/meshery-extensions
• You will have the opportunity to demonstrate progress and gather feedback during the weekly Meshery community development meetings.
• Upon successful completion and delivery, the volunteer(s) will become the official maintainer(s) of the Meshery MCP Server extension.

This is a high-visibility project within the Meshery ecosystem. It requires strong ownership, technical excellence, and a commitment to delivering production-quality work.

If you have the skills, time, and drive to take this on end-to-end, we want to hear from you and enable you with the opportunity to leave an indelible mark on Meshery (and yourself).

Please reply with your interest, relevant experience, and any initial thoughts on the approach.

- Meshery Maintainers

[Lucky Singh]

Hey myself lucky and I'm currently pursuing a Bachelor's degree in Computer Science, with a strong focus on backend development, web technologies, and software architecture. My technical proficiencies encompass Python, JavaScript, REST APIs, data structures and algorithms, Git/GitHub workflows, and full-stack application development. I have also gained experience through projects involving automation, management systems, and scalable web-based solutions.

The ownership aspect of this opportunity is particularly appealing to me. I am adept at working autonomously across the entire development lifecycle, including requirements analysis, architectural planning, implementation, testing, debugging, documentation, and deployment. I am committed to gaining a deep understanding of systems and developing maintainable, production-quality solutions.

My initial technical approach for the Meshery MCP Server Extension would involve:

* Thoroughly understanding Meshery's existing architecture, extension ecosystem, and MCP workflows.

* Reviewing current APIs, CLI integrations, and MeshModel components.

* Designing a modular and extensible server structure to ensure scalability and maintainability.

* Implementing clean API interfaces with robust error handling and comprehensive logging.

* Developing comprehensive unit and integration tests to guarantee reliability.

* Creating developer-focused documentation to facilitate onboarding and contribution workflows.

* Adhering to open-source best practices for CI/CD, version control, and collaborative development.

While I was not selected for GSoC this year, with Meshery as my top preference, I am eager to contribute to this role. I am confident that my contributions would be valuable, and I am prepared to actively participate in community discussions and iterate rapidly based on maintainer feedback. I view this project as an exceptional opportunity to deliver meaningful engineering work and further develop my expertise within the cloud-native and open-source ecosystem.

I would be grateful for the chance to contribute to this initiative. Please advise on the next steps, recommended resources, or areas where I can begin contributing immediately.

Thank you for your time and consideration. I look forward to your response.

Best regards,

Lucky Singh

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/fa4f15e4-fd99-4f8c-9f66-8b75671cefc0n%40meshery.io.

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAEa3fVe_p7ytYHxX9_KQEb6K8H7WPDdPgwPOiAhA9BWDOaO1kw%40mail.gmail.com.

[MUKUL RANA]

Dear Meshery Maintainers,

I’m excited to express my interest in contributing as a lead developer and maintainer for the Meshery MCP Server extension.

I enjoy building AI-powered developer tools and infrastructure-focused systems end-to-end, and this project strongly aligns with my interests in agentic workflows, developer experience, and scalable backend architecture.

Relevant experience:

- Built multiple full-stack AI systems using FastAPI, LangGraph, LangChain, vector databases, and modern cloud-native tooling.

- Experience designing production-ready architectures with strong focus on modularity, scalability, and maintainability.

- Worked on automation agents, AI copilots, retrieval systems, and developer productivity platforms.

- Comfortable independently handling the complete lifecycle: architecture, implementation, testing, documentation, deployment, and community collaboration.

Initial thoughts on the approach:

- Design the MCP Server as a modular and extensible service with clean abstractions for Meshery design generation workflows.

- Implement structured tool interfaces and schema-driven interactions to support reliable AI-agent communication.

- Add strong testing coverage (unit + integration tests) and developer-friendly documentation from the beginning.

- Ensure the extension is easy to integrate into MCP ecosystems and compatible with relevant MCP/Skills marketplaces.

- Maintain transparency through regular demos and feedback loops during community meetings.

I’m particularly excited about the opportunity to contribute something impactful to the Meshery ecosystem while collaborating closely with the community.

Relevant profiles:

GitHub: github.com/mukulpythondev

LinkedIn: https://linkedin.com/in/mukul-webdev

Technical Articles/Blogs: https://mukul-rana.hashnode.dev

Looking forward to hearing from you and discussing the next steps.

Best regards,

Mukul Rana

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAMkJ6JU3-n16G7%3DnCswW09a%2BnZQj7qDNnY%2BhsyGMbq%2B9myXxSQ%40mail.gmail.com.

[Lucky Singh]

Hey myself lucky and I'm currently pursuing a Bachelor's degree in Computer Science, with a strong focus on backend development, web technologies, and software architecture. My technical proficiencies encompass Python, JavaScript, REST APIs, data structures and algorithms, Git/GitHub workflows, and full-stack application development. I have also gained experience through projects involving automation, management systems, and scalable web-based solutions.

The ownership aspect of this opportunity is particularly appealing to me. I am adept at working autonomously across the entire development lifecycle, including requirements analysis, architectural planning, implementation, testing, debugging, documentation, and deployment. I am committed to gaining a deep understanding of systems and developing maintainable, production-quality solutions.

My initial technical approach for the Meshery MCP Server Extension would involve:

* Thoroughly understanding Meshery's existing architecture, extension ecosystem, and MCP workflows.

* Reviewing current APIs, CLI integrations, and MeshModel components.

* Designing a modular and extensible server structure to ensure scalability and maintainability.

* Implementing clean API interfaces with robust error handling and comprehensive logging.

* Developing comprehensive unit and integration tests to guarantee reliability.

* Creating developer-focused documentation to facilitate onboarding and contribution workflows.

* Adhering to open-source best practices for CI/CD, version control, and collaborative development.

While I was not selected for GSoC this year, with Meshery as my top preference, I am eager to contribute to this role. I am confident that my contributions would be valuable, and I am prepared to actively participate in community discussions and iterate rapidly based on maintainer feedback. I view this project as an exceptional opportunity to deliver meaningful engineering work and further develop my expertise within the cloud-native and open-source ecosystem.

I would be grateful for the chance to contribute to this initiative. Please advise on the next steps, recommended resources, or areas where I can begin contributing immediately.

Thank you for your time and consideration. I look forward to your response.

Best regards,

Lucky Singh

GitHub : https://github.com/luckyxhq

LinkedIn : https://www.linkedin.com/in/lucky-singh-4363a2lb5?utm_source=share&utm_campaign=share_via&utm_content=profile&utm_medium=android_app

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAEa3fVdfw8VFs-KwWTcmgmzdNB7Vm0iyZwDKvfhZN_dankxJGw%40mail.gmail.com.

[Ragul Balajii]

Dear Meshery Maintainers,

I’m Ragul Balajii, currently pursuing an M.Sc. (Integrated) degree, and I have been actively contributing to the Layer5 and Meshery community for the past few months. I also have experience with Python and software development projects, along with a 6-month internship period ahead during which I’ll be able to dedicate consistent time toward contributing and learning.

I would like to express my interest in contributing to the Meshery MCP Server project. I’m interested in learning more about MCP and exploring how it can be integrated with Meshery to simplify and improve design creation workflows.

My initial approach would be to first understand the existing Meshery architecture and MCP workflows, then begin with a simple working prototype and gradually improve it with proper testing, documentation, and community feedback.

I’m genuinely interested in contributing consistently, learning throughout the process, and collaborating with the community on this project.

Thank you for the opportunity.

Regards,
Ragul Balajii.

GitHub: https://github.com/Sbragul26/

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/79e49391-0890-4ec7-936c-6ea43ea4c244n%40meshery.io.

[Yash Nagar]

Dear Lee Calcote and Meshery Maintainers,

I am writing to express my strong interest in the Meshery MCP Server Extension project. My name is Yash Nagar, and I am currently pursuing my Master’s in Computer Applications (MCA).

I have a deep interest in this specific extension because I have already built a similar autonomous system using the Model Context Protocol (MCP). During the Google Cloud Agent Builder Hackathon, I developed an AI assistant designed for "Assistant Triage." It automatically fetched data sync failures from Fivetran via MCP and alerted developers with specific suggestions on how to fix the pipeline errors.

I am eager to apply my experience with agentic workflows to help Meshery users build infrastructure designs using natural language. If you find my background valuable, I would love the chance to lead or contribute to this effort from 0% to 100%.

GitHub: yashnagar67 Portfolio: yashnagarkota.in

Best regards,

Yash Nagar

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/764b54dc-87aa-4cef-84fa-c7d2b6ed777cn%40meshery.io.

[Sarang Bodhe]

Subject: Volunteer Interest — Meshery MCP Server Extension

Hi Lee,

My name is Sarang Bodhe. I'm a CSE (AI & ML) student from Bangalore, and I want to build the Meshery MCP Server Extension.

Not because it looks good on a resume. Not because someone told me to apply. Because I've been inside this codebase, I understand what Meshery is trying to do, and I genuinely believe I can deliver this.

I've been contributing to the Meshery ecosystem, and what that experience has given me isn't just merged code it's a real understanding of how this project is architected, what the community values, and what "production-quality" actually means here. Every contribution taught me something I couldn't have learned from just reading docs. That's the kind of learning you can't fake, and it's exactly what makes me confident I can take this from 0 to 100 without getting lost halfway.

On the technical side I work at the exact intersection this project demands. AI/ML systems and cloud-native backend infrastructure aren't separate worlds for me, they're what I spend my time in. I don't just know what MCP is I understand it as an architecture: how you expose tools cleanly, how you define schemas that AI agents can actually trust, how you make something that doesn't break the moment it leaves a demo environment. That's what I intend to build.

Here's how I'd approach it:

Before writing a single line of code, I'd spend real time inside Meshery's extension patterns, MeshModel APIs, and the design creation workflows  because the worst thing I could do is build something technically correct but architecturally wrong for this ecosystem. Then I'd design the MCP Server with clean, schema-driven tool interfaces built for reliability, not just the happy path. Tests, CI, and docs come in from day one  not polished at the end. I'd show up to every community meeting, share progress honestly, and treat feedback as part of the build process. And when it's done, I'd own the push into MCP and Skills marketplaces myself  because delivery means shipped and visible, not just merged.

You wrote that this project is a chance to leave an indelible mark on Meshery. That line stayed with me because that's exactly how I think about open source contribution. Not as a transaction, but as something you build with care and stand behind long after it ships.

I'm also applying for LFX Mentorship, and this project is a big part of why. But I want to be clear this volunteer role isn't contingent on that. Whether or not LFX works out, I want to build this.

I'm ready to start now.

Sarang Bodhe
GitHub: https://github.com/Tomgrinds777
LinkedIn: https://www.linkedin.com/in/sarang-s-bodhe
Twitter: https://x.com/SHREE272006
Email: sarangbo...@gmail.com

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/f3108f19-9a9b-4a7d-9665-f8f96ae2f292n%40meshery.io.

[Akshay]

Hi Lee,

I'm Akshay Sriram — CS+AI/DS undergrad at IIIT Kottayam, active Meshery
contributor (Sistent PR #1493 approved, CMC certified across all 5 units,
attending weekly Newcomers meetings).

I've already built the BYOM multi-provider architecture this project
requires. My AEO Diagnostic + Meshery AI Adapter prototype
(aeo-diag-akshay.vercel.app) queries Groq, Cohere, and Ollama in parallel
with structured JSON output — the same provider abstraction pattern an MCP
server needs. It's live and queryable today.

My approach for the Meshery MCP Server:
- Design schema-driven MCP tool interfaces aligned with Meshery's
  existing MeshModel and design creation APIs
- Implement clean provider abstractions in Go using MeshKit patterns
  I've already studied
- Build test coverage from day one, not polished at the end
- Show up to every community meeting and ship transparently

I'm also applying for LFX Mentorship 2026 Term 2 for the AI Adapter
project — this MCP Server aligns directly with that work and I'd love to
contribute to both.

I'm ready to start now.

Akshay Sriram
Github  | aeo-diag-akshay.vercel.app

Linkedin

Portfolio

On Friday, May 15, 2026 at 11:05:13 PM UTC+5:30 lee.c...@layer5.io wrote:

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/7e0bac03-0bd5-4316-b5e0-9fcbde46c246n%40meshery.io.

[Shibu Gope]

Hi Meshery Maintainers,

I’m very interested in contributing to and potentially maintaining the Meshery MCP Server extension.

I currently work as a Software Developer and have experience building backend systems, APIs, and full-stack applications using technologies including Java, Spring Boot, Node.js, React.js, PHP, Redis, Kafka, Docker, Kubernetes, and AWS.

Some of my previous work includes:

* Building scalable backend systems and REST APIs using Spring Boot and MySQL

* Developing microservices-based applications with Kafka and Redis

* Working on full-stack HRMS and web platforms using React.js, Node.js, MongoDB, and PHP

* Integrating AI models and automation features into production applications

I’m also a self-taught developer, which has helped me become highly self-directed and comfortable learning and implementing new systems independently. I enjoy taking ownership of projects end-to-end — from architecture and implementation to testing, debugging, deployment, and documentation.

What particularly interests me about this project is the opportunity to contribute to the Meshery ecosystem in a meaningful way and build something that developers can actively use to accelerate design workflows through MCP.

My initial thoughts on the approach would be:

* Define a modular MCP server architecture with clear separation between Meshery interaction layers and MCP tooling logic

* Build extensible APIs/actions for generating and managing Meshery designs

* Focus early on strong testing and developer experience

* Ensure the extension is easy to publish, maintain, and extend within the Meshery ecosystem

* Keep documentation and onboarding simple for contributors and users

I’m comfortable collaborating in open-source environments, sharing progress regularly, and iterating based on community feedback during development meetings.

I would love the opportunity to contribute and help drive this project from concept to production-quality delivery.

Thank you for your consideration.

Shibu Gope

LinkedIn:- https://www.linkedin.com/in/shibu-gope-8a0543247

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CA%2BH22fcQGgHJbzrsCNbq%3DvThCj4QcnvjaEu60BmG%2B0Gn0%3DhrcQ%40mail.gmail.com.

[Rahul Rudra]

Dear Lee and Meshery Maintainers,

I am writing to express my strong interest in contributing to and maintaining the Meshery MCP Server Extension project.

I am a full-stack software engineer at YBIntel, where I lead the architecture and development of production-grade AI-powered SaaS systems. My professional experience includes:

  - Backend & Infrastructure: Developing systems in Python/FastAPI and Node.js, and managing AWS infrastructure (Lambda, SQS, RDS, and CI/CD).

  - AI Integration: Implementing AI workflows using OpenRouter and Azure OpenAI with structured outputs and provider abstractions.

  - Frontend: Building applications with Next.js and TypeScript.

In addition to my professional role, I have been an active contributor to the Layer5 and Meshery ecosystem. I am comfortable taking full ownership of a project’s lifecycle, from initial architecture and implementation to testing, documentation, and long-term maintenance.

My proposed approach for the Meshery MCP Server includes:

1. Analysis: Conducting a deep dive into current Meshery architecture, MeshModel workflows, and the extension ecosystem.

2. Design: Architecting a modular server structure with clean abstractions for long-term extensibility.

3. Implementation: Building robust API interfaces with integrated observability, validation, and automated testing.

4. Delivery: Ensuring production readiness through comprehensive documentation and automated CI/CD pipelines.

5. Collaboration: Iterating transparently based on community feedback during weekly meetings.

I am eager to build a foundational component for Meshery that enhances AI-assisted developer workflows. I would appreciate the opportunity to discuss next steps or specific areas where I can begin contributing immediately.

Best regards,

Rahul Rudra

GitHub: https://github.com/rudra

LinkedIn: https://www.linkedin.com/in/rahul-rudra/

On Fri, 15 May, 2026, 11:05 pm 'Lee Calcote' via Meshery Developers, <devel...@meshery.io> wrote:

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/fa4f15e4-fd99-4f8c-9f66-8b75671cefc0n%40meshery.io.

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAK8VkwOkn%3DPLf%2BLwkoMuR%2B8zWdbE%2B_V6XYVExRmMz3sP8Rc4ww%40mail.gmail.com.

[Chethan AC]

Subject: Re: Meshery MCP Server - Intrested to work on this

Hi Lee,

This feels like a full-circle moment. I recently reached out to you on LinkedIn asking about opportunities to contribute more meaningfully to Meshery and here this is. 

A bit about where I'm coming from: I'm Chethan, a third-year  student at Dayananda Sagar College of Engineering, Bengaluru.I have been active across CNCF projects including KubeArmor, OpenCost, Jaeger, and others - working across UI, backend logic, metrics, and security components. I've also independently built and shipped full-stack projects from scratch, which has given me a real appreciation for what "production quality" actually means.

My initial thoughts on the MCP Server approach:
- Start by thoroughly mapping Meshery's design creation APIs before writing a line of code — understanding what needs to be exposed as MCP tools and resources is the foundation
- Architect it for extensibility from day one, so adding capabilities later doesn't mean reworking the core
- Build tests and docs alongside the implementation, not as an afterthought
- Research MCP and Skills marketplace submission requirements early so publication isn't a last-minute scramble

I'm ready to own this end-to-end  architecture, implementation, testing, documentation, and marketplace publication. And I'll be at the weekly community meetings to share progress and get feedback the whole way through.

Thank you for creating this opportunity

Warmly,
Chethan Anathahalli Cheluvaraju
+91 7204199035 | acche...@gmail.com
Github- github.com/chethanac15

Linkedin- https://www.linkedin.com/in/chethanac15

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.
To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/fa4f15e4-fd99-4f8c-9f66-8b75671cefc0n%40meshery.io.

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CA%2BwKr%3D7LTyS49c2ZP%2B4UV5kh_r4ZRSwZ--bD8RrRw7kEw5uaHA%40mail.gmail.com.

[ANMOL]

Hi Meshery Maintainers,

I’m interested in contributing as a solo contributor for the Meshery MCP Server extension project.

I have 1+ year of experience working with Node.js and TypeScript, primarily focused on backend APIs, AI integrations, extension/plugin systems, and developer tooling. I’ve also contributed to multiple open source projects and genuinely enjoy building developer-focused products and infrastructure.

GitHub: https://github.com/anmolsah

What especially interests me about this project is the opportunity to work on something that sits at the intersection of AI workflows, MCP tooling, and cloud-native infrastructure. I like projects that require ownership from architecture to delivery, and this seems like exactly that kind of challenge.

My initial thought for the approach would be to design the MCP server in a modular way so that:

- Meshery design generation capabilities can be exposed cleanly through MCP tools/resources

- The extension remains extensible for future Meshery workflows

- AI clients and agents can reliably interact with Meshery through structured schemas and predictable tool contracts

- Testing and documentation are integrated from the beginning instead of added later

I’m comfortable independently handling:

- Architecture and implementation

- API/tool design

- Documentation

- Testing

- Iterative improvements through community feedback

I’d be excited to participate in the weekly community meetings, share progress transparently, and work toward delivering a production-quality extension for the Meshery ecosystem.

Looking forward to contributing.

Thanks,

Anmol Sah

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CANcXJJV8g-y38RYpNtbc29kcS2Rq%2B60MZU1wq6B8%2BufPWkJ78A%40mail.gmail.com.

[Manish Kumar]

Hi Lee and the Meshery Maintainers,

I'm Manish, and I want to build the Meshery MCP Server Extension.

I've contributed 3 PRs to meshery-extensions/shape-builder — the extension under the exact same GitHub org where this repo will live. I fixed a broken ESLint v9 flat config blocking the dev environment, resolved a copy-to-clipboard failure on long coordinate strings, and designed a modal UX for polygon coordinate display. Each required understanding how Meshery extensions are structured at the boundary, not just how to write JavaScript.

I also have 2 PRs to meshery/meshery.io documenting the Shape Builder on the public extensions page. This project explicitly lists publication and socialization into MCP and Skills marketplaces as a deliverable — I've done that exact step before and know what it actually takes.

Beyond Meshery, I've contributed to KubeEdge (2 PRs), so Kubernetes-native patterns aren't new territory.

My approach:

Week 1–2 (audit before code): Map every design creation workflow in Meshery to a specific MCP tool contract — Design API, MeshModel schemas, Catalog endpoints, CLI integrations. This produces a tool interface spec I'll share at the first community meeting before building starts.

Week 2–4 (core server): Go + MeshKit patterns. Two transports from day one: stdio for local (Claude Desktop, Cursor, VS Code) and SSE/HTTP for remote. JSON Schema validation on every input before it touches the Meshery API client — no silent failures, no hallucinated fields getting through.

Initial tools: meshery_create_design, meshery_list_designs, meshery_deploy_design (with dry-run), meshery_get_components, meshery_get_patterns, meshery_get_connections.

Week 4–6 (hardening): Auth token injection per request, structured error codes agents can reason about, retry/timeout logic, unit + integration tests against a live Meshery instance in CI.

Week 6–8 (policy tools): Meshery recently ported OPA/Rego to native Go — that opens meshery_validate_design and meshery_apply_policy, making the server useful for AI-assisted policy validation before any infrastructure change goes out.

Week 8–10 (publication): MCP marketplace, Skills marketplace, getting-started guide (stdio + SSE + Claude Desktop config), live demo at a community meeting — full flow from AI agent to deployed design.

I can tell you specifically which Meshery API endpoints map to which MCP tools, why the ESLint v9 config was failing in shape-builder, and what the extensions page needs to list a new extension correctly. That's not theory — it's from work already in your repos.

Ready to start the architecture audit immediately.

GitHub: https://github.com/manishpatel00
LinkedIn: https://www.linkedin.com/in/manishpatel005/

Best regards,
Manish

On Friday, May 15, 2026 at 11:05:13 PM UTC+5:30 lee.c...@layer5.io wrote:

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/cfd10b9f-3005-4ead-b4ea-9cf0ed8a90fbn%40meshery.io.

[kaira Khanna]

Hello All,

Thank you for sharing this opportunity.

I am interested in contributing as a volunteer maintainer for the Meshery MCP Server Extension. I am a Computer Science student with experience in software development, Java, Python, web development, and AI-related projects. I would love to learn more about the contribution process and how I can get started.

Looking forward to your response.

Best regards,

Anushka

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/CAHtiujfoufWUy65bPo7rK7sE9MoQ90Bv10nehMuofKXzNMyrow%40mail.gmail.com.

[Cooper Fitzgerald]

Hello Meshery community,

The Meshery MCP Server initiative now has a home (a new repo) and it's open for contribution:

 - https://github.com/meshery-extensions/meshery-mcp-server

As an official Meshery Extension, it will streamline and accelerate how Meshery designs are created. In the spirit of what Lee outlined for this initiative, the MCP Server is owned by its maintainers end-to-end:  architecture and design, implementation, tests, documentation, and publication to both the MCP and Skills marketplaces. Contributors who carry that work through independently become the project's official maintainer(s).

Initial scope in priority order:

1. Creation of Meshery designs

2. Retrieval in user's requested file format.

2. Snapshotting of Meshery designs

3. Design deployment dry-run results

4. Definition, invocation, and results of performance tests

No invitation required: anyone capable of and available to take on that full-lifecycle ownership is welcome to step in. Existing maintainers will offer support and assistance to competent contributors. A few good ways to start:

- Open a thread on the discussion forum (https://discuss.meshery.io) to propose and align on architecture and confirmation of scope.
- File Issues for the initial building blocks so work can proceed in parallel.
- Send your first PRs - foundational ones (scaffolding, CI, a design doc) are a great place to begin.

The repository was created from Meshery's standard template, so the contributing, governance, and code-of-conduct guides are already in place, however, any number of workflows need to be removed and the README cleaned up. Introduce yourself in https://discuss.meshery.io and dive in.

Looking forward to supporting you,
Cooper

Meshery maintainer

[Yi Nuo]

To help organize, 14 new issues have been created by Cooper, me, Pontus, and Jill - https://github.com/meshery-extensions/meshery-mcp-server/issues

Yi Nuo

[Mayank Sharma]

Hi Team,

I would like to take up this Meshery MCP server issue and could be take this end to end.

Let me know how to proceed and such. 

Thanks & Regards,

Mayank Sharma

--

You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/c4c4a2f0-3463-48fd-8ef0-b2422e9b1616n%40meshery.io.

[Lee Calcote]

Cooper, Yi, someone to empower. Please do.  

- Lee

Begin forwarded message:

From: Omolade Akinwumi <akinwumi...@gmail.com>
Date: July 28, 2026 at 1:08:53 AM CDT
To: Lee Calcote <lee.c...@layer5.io>
Subject: Re: [meshery-dev] Call for Volunteer Maintainer: Meshery MCP Server Extension



Hi Lee, and Meshery team,

I want this one. I've been hands-on with both Meshery and MCP servers, and reading this call felt like it was written for exactly the intersection I sit in.

A little about me: I'm a Senior DevOps and Cloud Infrastructure Engineer with 7+ years across fintech and payments, and an AWS Community Builder. My day to day covers Kubernetes based infrastructure (including EKS), GitOps workflows, Infrastructure as Code with Terraform, secure secret management, and observability stacks like Prometheus and Grafana for production grade platforms. But more than the toolset, I'm someone who has taken a product from a blank repo to production and stood behind it the whole way. I co-founded a proptech startup where I was CTO and owned everything from architecture to delivery. I know what it costs to carry something from 0% to 100%, and I don't shy away from that.

I've also been actively involved in Kyverno through its full CNCF journey. I watched it move from sandbox through incubation to Graduated, including its announcement in March 2026, so I understand first hand the due diligence and governance standards a project has to meet to earn that kind of trust. I've given presentations on Kyverno and policy as code at KyvernoCon, including a talk on drift prevention in GitOps workflows. That's exactly why the "become the official maintainer" framing here doesn't scare me off. I've seen up close what real maturity and stewardship look like in a CNCF ecosystem, and I want to help build that here.

On approach:
1. Map the MCP Server's core tool surface against Meshery's existing design creation APIs, starting with the highest leverage flows first.
2. Stand up the repo in meshery-extensions with CI, linting, and test scaffolding in place before the first feature lands, so coverage and observability are built in, not retrofitted.
3. Show up at the weekly community dev meetings with real progress, and adjust based on what the community actually needs.
4. Finish with clear documentation, including content suitable for Meshery Academy, and get it published into the relevant MCP and Skills marketplaces.

Beyond the technical build, I care about mentorship and community. I regularly lead cohorts in DevOps and cloud engineering, and I'd bring the same care to reviewing contributions and keeping the project welcoming as it grows.

Looking forward to your response
Best,
Omolade

On Fri, May 15, 2026 at 7:40 PM 'Lee Calcote' via Meshery Developers <devel...@meshery.io> wrote:

We are looking for one or more serious, experienced, and self-directed contributors to build a new official Meshery Extension: the Meshery MCP Server.

Project Focus

This extension will provide a dedicated MCP Server that streamlines and accelerates the creation of Meshery designs.

Requirements

• You must be capable of independently defining, architecting, implementing, testing, and fully delivering the project from 0% to 100%.
• The completed extension must include:
  • Full functionality
  • Comprehensive tests
  • Basic documentation
  • Publication / socialization into relevant MCP and Skills marketplaces

Project Details

• The repository will be created under the official organization: https://github.com/meshery-extensions
• You will have the opportunity to demonstrate progress and gather feedback during the weekly Meshery community development meetings.
• Upon successful completion and delivery, the volunteer(s) will become the official maintainer(s) of the Meshery MCP Server extension.

This is a high-visibility project within the Meshery ecosystem. It requires strong ownership, technical excellence, and a commitment to delivering production-quality work.

If you have the skills, time, and drive to take this on end-to-end, we want to hear from you and enable you with the opportunity to leave an indelible mark on Meshery (and yourself).

Please reply with your interest, relevant experience, and any initial thoughts on the approach.

- Meshery Maintainers

--
You received this message because you are subscribed to the Google Groups "Meshery Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@meshery.io.

To view this discussion visit https://groups.google.com/a/meshery.io/d/msgid/developers/fa4f15e4-fd99-4f8c-9f66-8b75671cefc0n%40meshery.io.

[Akash K.G.]

Hi Lee, Cooper, Yi Nuo, and the Meshery maintainers, 

I'm Akash Naickar, a pre-final year BTech CSE student. I've been working on meshery-extensions/meshery-mcp-server since the repo went live, and wanted to share where things stand.

What I've shipped here
- PR #28 - the repo scaffold: MCP server foundation on mark3labs/mcp-go with stdio support, config, Makefile/Dockerfile, plus a fix for the repo's previously-broken CI (removing workflows that referenced non-existent ui//provider-ui/ dirs). CodeRabbit-approved, with an end-to-end server_test.go (Initialize → ListTools → CallTool).
- Issue #6 (ready behind it) - a Meshery REST client with a meshery_ping tool, built and tested, ready to open the moment the scaffold lands.

Upstream contributions
I contribute across open source: a new noExtendNative lint rule in biome, a new pdfioFileCreateFontObjFromSystem font API in pdfio, and docs/bug fixes in pandas plus fixes to pandas and freenet-core currently in review.

Why this project
The intersection of AI, MCP, and cloud-native infrastructure is where I want to grow. Designing tools an AI agent can reliably call against real infrastructure is the most interesting engineering problem I've come across, and this project is a hands-on way to own that end-to-end foundational PRs first (scaffold + CI), then the client, then tools.

Where I'm headed
My focus is a production-grade server on mark3labs/mcp-go with clean REST/GraphQL integration to Meshery, tests and docs from day one, and owning publication into the MCP/Skills marketplaces. I'm applying for the Term 3 LFX MCP Server slot, but I'll keep contributing regardless of that outcome.

I'll be at the weekly community meetings to share progress and take feedback.

Thanks 
Akash Naickar
GitHub: AkashNaickar(https://github.com/AkashNaickar)

On Monday, August 3, 2026 at 11:26:55 PM UTC+5:30 ISHWAR CHAND MEENA wrote:

Hi everyone,

I wanted to follow up now that the repository is live.

I've been contributing to Meshery since around May, primarily on the Go/backend side through bug fixes, reviews, and issue triage. Today I started contributing to the MCP Server repository by reviewing the initial scaffold PR and opening a follow-up issue around the repository's CI/workflow setup.

What draws me to this project is the chance to build an extension from the ground up. Contributing and reviewing over the past few months has taught me a decent amount about Meshery's backend and architecture, and there's still a lot for me to learn. Working on an MCP server that builds on those capabilities feels like a natural next step, and I'm looking forward to contributing across implementation, reviews, testing, and the overall project as it evolves.

I'm also planning to apply for the CNCF LFX mentorship, but regardless of the outcome I'll continue contributing to the project.
Regards, 
Ishwar chand.
Github: https://github.com/ishwar170695

[Akash K.G.]

[ISHWAR CHAND MEENA]

Hi everyone,

I wanted to follow up now that the repository is live.

I've been contributing to Meshery since around May, primarily on the Go/backend side through bug fixes, reviews, and issue triage. Today I started contributing to the MCP Server repository by reviewing the initial scaffold PR and opening a follow-up issue around the repository's CI/workflow setup.

What draws me to this project is the chance to build an extension from the ground up. Contributing and reviewing over the past few months has taught me a decent amount about Meshery's backend and architecture, and there's still a lot for me to learn. Working on an MCP server that builds on those capabilities feels like a natural next step, and I'm looking forward to contributing across implementation, reviews, testing, and the overall project as it evolves.

I'm also planning to apply for the CNCF LFX mentorship, but regardless of the outcome I'll continue contributing to the project.
Regards, 
Ishwar chand.
Github: https://github.com/ishwar170695

On Friday, May 15, 2026 at 11:05:13 PM UTC+5:30 Lee Calcote wrote:

[Yatharth Katta]

Hello Meshery Maintenance Team,

I would like to offer to assist with the building and maintenance of the Meshery MCP Server.

Instead of simply stating my interest, let me clarify how I would assess success.

A useful MCP server should not only offer Meshery's APIs but also provide design capabilities at a higher level that can be utilized by an LLM. The MCP layer does not serve its purpose if the agent still has to be aware of the internals of Meshery while deploying.

My initial step will consist of finding the smallest set of tools that give access to the greatest number of design workflows such as:

• creating and changing designs,
• finding components in the MeshModel,
• checking configurations and relationships,
• producing complete designs from structured intent,
• and refinements of the already existing designs.

From that point on, I will concentrate on three important elements equally:

• a clean schema-based architecture of the server that is easy to expand,
• deterministic behavior of tools with thorough tests,
• improvement of the experience and satisfaction of developers through documentation, examples, and repeatability.

The types of projects that I find most interesting involve interface design instead of merely implementing various endpoints. The MCP server is an essential part of other developers' thought processes. Therefore, it needs to be consistent, easy to use, and need to produce predictable results.

My experience thus far has mostly been in full-stack development, development of AI-integrated applications, as well as in developing production-ready software. I have done work at all stages of the development process, from architecture design all the way to deployment and long-term support.

If given this task, I would consider it as developing a product rather than a coding task. I would like to create a plugin that people will want to use, document it well enough for others to improve it, and support it afterward.

I appreciate your attention to my application.
Yatharth Katta
GitHub: https://github.com/yats0x7

On Monday, August 3, 2026 at 11:26:55 PM UTC+5:30 ISHWAR CHAND MEENA wrote:

[Armaan Shukla]

Hi Lee and Meshery Maintainers,

I’d like to express my interest in contributing to the Meshery MCP Server and helping with its development and maintenance.

I’m currently a Software Engineer at Oracle, where I work on software development, debugging, testing, and collaborating with other engineers across the development lifecycle. This has helped me become comfortable working with existing systems, understanding codebases, and taking ownership of changes from implementation through review and validation.

I’m interested in Meshery because of its work around cloud-native infrastructure and the opportunity to contribute to a project that is still being built from the ground up. The MCP Server looks like a good place to contribute meaningfully across implementation, testing, documentation, and overall project quality.

My initial approach would be to first understand the existing Meshery architecture, MeshModel, APIs, and the current state of the MCP Server repository. From there, I’d like to pick up well-defined issues, contribute to the core implementation, add tests alongside changes, and help improve documentation and developer experience as the project evolves.

I’m also comfortable taking ownership of work end-to-end rather than limiting myself to small fixes. I’d be happy to participate in the weekly community meetings, share progress, take feedback, and continue contributing to the project over the longer term.

Please let me know what would be a good area or issue to start with. I’d be glad to jump in and contribute.

Thanks,
Armaan Shukla
Software Engineer, Oracle
GitHub: https://github.com/ice-009
LinkedIn: https://www.linkedin.com/in/armaanshukla/

--

[Debajit Roul]

Hi Lee and Meshery Maintainers,

I would like to volunteer for the development and maintenance of the Meshery MCP Server.

At the moment, I’ve been actively learning and contributing around Meshery, particularly mesheryctl, and I’ve also applied for the LFX Mentorship project focused on mesheryctl. That work has been helping me understand the Meshery codebase, its architecture, testing practices, and contributor workflow more deeply.

While mesheryctl is currently the area I’m spending the most time on, I’m also very interested in the MCP Server and would be happy to contribute here as well, regardless of the outcome of the mentorship selection.

I’m particularly interested in understanding how the MCP Server interfaces with MeshModel and Meshery’s APIs, and in contributing wherever there is a need—whether that is implementation, testing, documentation, or improving the overall developer experience.

I’m still learning the broader Meshery ecosystem, so I’d prefer to demonstrate my interest through actual contributions and gradually take on more ownership as I become more familiar with the project.

Looking forward to contributing and learning from the community.

Best,
Debajit Roul
GitHub: https://github.com/Debagithub567

On Friday, May 15, 2026 at 11:05:13 PM UTC+5:30 lee.c...@layer5.io wrote:

[DINESH]

Hello,
I am Paluvadi Dinesh Manideep(dineshm...@gmail.com  Linkedin    Github) , from India .
So I want to express my interest in working in this project of building MCP Server Extension for the Meshery project 
Request:
So i want to make it clear that I Request the maintainers that i am open to any other project also , So my main goal is to Contribute to a repository like Meshery with a team of Contributors build a Big feature.
I am more intersted in the process of development of the feature and successfully integrating into the project.
Motivation :

I started Open Source development seeing my seniors contribute to different repositories.

The most interesting part I feel in this contribution is the ability to write code which will be used by many people in the real world. 

In particular to MCP server project the exciting part is designing the protocol from the ground up. Previous contributions I have made a small change and made a pr , So that i could understand the contribution style of the repository Technical Skills I have mostly developed full stack applications and C++ projects in the past and I have been learning go past few days.

On Friday, May 15, 2026 at 11:05:13 PM UTC+5:30 lee.c...@layer5.io wrote: