microsoft / microsoft/markitdown
Running behind a corporate proxy requires additional configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 186k
- Forks
- 13.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
When running behind a corporate on MacOS, you'll need to add an environment variable to your mcp.json file.
"microsoft/markitdown": {
"type": "stdio",
"command": "uvx",
"args": [
"markitdown-mcp==0.0.1a4"
],
"env": {
"SSL_CERT_FILE": "/Library/Application Support/VPNCLIENT/Agent/data/cacert_combined.pem"
},
"gallery": "https://api.mcp.github.com/2025-09-15/v0/servers/976a2f68-e16c-4e2b-9709-7133487f8c14",
"version": "1.0.0"
}
Without this uvx can't pull down python libraires without and error since the coproprate proxy will 'man-in-the-middle' the requests, resulting in a different cert being seen by python.
Might want to add that to the docs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the documentation for configuring the MCP server and review its existing setup examples. Add the macOS corporate-proxy case using the SSL_CERT_FILE environment variable in mcp.json, then verify that the example is valid JSON and clearly explains why uvx needs the certificate bundle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100