#1115742 ITP: python-mcp -- Python SDK for Model Context Protocol

Package:
wnpp
Source:
wnpp
Submitter:
Michael Fladischer
Date:
2026-06-28 08:25:01 UTC
Severity:
normal
#1115742#5
Date:
2025-09-19 18:18:49 UTC
From:
To:
* Package name    : python-mcp
  Version         : 1.14.1
  Upstream Contact: Anthropic, PBC
* URL             : https://github.com/modelcontextprotocol/python-sdk
* License         : Expat
  Programming Lang: Python
  Description     : Python SDK for Model Context Protocol


 The Model Context Protocol allows applications to provide context for LLMs in a
 standardized way, separating the concerns of providing context from the actual
 LLM interaction. This Python SDK implements the full MCP specification, making
 it easy to:
 .
  * Build MCP clients that can connect to any MCP server
  * Create MCP servers that expose resources, prompts and tools
  * Use standard transports like stdio, SSE, and Streamable HTTP
  * Handle all MCP protocol messages and lifecycle events

I intend to maintain this as part of the DPT but I am open to have it on the
Debian Deep Learning Team (not a member yet).
-----BEGIN PGP SIGNATURE-----

iQFPBAEBCgA5FiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmjNnoYbHGZsYWRpc2No
ZXJtaWNoYWVsQGZsYWRpLmF0AAoJEP/TyIuZfdFqfqMH/jSw2oFHoyWvzDvYmBS9
eWNEPUBiQgmgU4fbefhOVlD6wPtNshslKcLBCzaqLSyiTyX3AlsZakS5cjc3wAsE
GMg/86X3+OH+10dHd7ajxrx0c574Xo9rxN5SRgFNlS+guXXHFNycNOBlK22fnhp9
O1g5xCK6uA4sU0DV66DeQ/mIoqU2/wXcIkjt6Iu6DbJoANnwhV0v6xEK12t/Kkl3
VF3PPkgrf1PjATf8hskwulQdZL+P5HvkGzfvj+feviOwSvIf4mz4K3Jx7QWrsisR
qhe/Nl3dsakAk78CWG4E6ZTICVMIYfTAd2rqCbzrQQn0nmkSq1Pu2RJXmqEWz1tE
MIk=
=KHjE
-----END PGP SIGNATURE-----
#1115742#12
Date:
2026-06-24 20:16:52 UTC
From:
To:
Hi Michael,

Have you started work on this? I am working at getting the tests to pass at the
moment.

I haven't pushed to salsa yet. I was considering to push it to the
homeassistant dependencies.

Br,

Pieter
#1115742#17
Date:
2026-06-24 20:16:52 UTC
From:
To:
Hi Michael,

Have you started work on this? I am working at getting the tests to pass at the
moment.

I haven't pushed to salsa yet. I was considering to push it to the
homeassistant dependencies.

Br,

Pieter
#1115742#22
Date:
2026-06-25 05:59:30 UTC
From:
To:
I kept some notes in d/README.Debian
#1115742#27
Date:
2026-06-25 05:59:30 UTC
From:
To:
I kept some notes in d/README.Debian
#1115742#32
Date:
2026-06-25 08:04:23 UTC
From:
To:
Hi Pieter,

I have started with the packaging but i did only the most rudimentary tasks.
In the meantime we dropped MCP (and LLMs) at work, so I have no further
interest in packaging this. You can just take over the ITP. I should have
turned it into a RFP last year anyways.

Regards,
Michael
#1115742#37
Date:
2026-06-28 08:21:50 UTC
From:
To:
Dear Python team,

I've packaged anthropics MCP python SDK because it is a dependency for home
assistant.

Package is at https://salsa.debian.org/python-team/packages/python-mcp

There was an ITP bug at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115742

Can someone please review my work? If its fine, upload it or give me upload
rights? Not sure if that can work on new packages?

Two questions I have:
1. I added a man page. I created that from markdown, but to keep pandoc out of the
build process I manually converted the md to troff and kept both in the debian
dir. Is that fine or should I build the troff file from my markdown source?

2. I now have the second package that uses network calls during tests. They
break in gbp buildpackage because I use auto-apt-proxy. I work around that with
a fixture unsetting HTTPS?_PROXY env vars. Is that the way to go? I doubt we
want to bother all upstream packages to unset HTTPS?_PROXY vars like that?

Thanks in advance,

Pieter