Skip to main content
Glama
CHANGELOG.md1.55 kB
# Changelog ## 0.1.11 - Added glama support ## 0.1.10 - smithery deployment work to get a bettwe score. enriched server.js, added mcp.json and an icon address. ## 0.1.9 - smithery deployment work ## 0.1.8 - smithery.yaml and Docker file fixes and added a entrypoint.sh to read environment variables and passes them as flags to docdexd ## 0.1.7 - Added smithery.yaml and Docker files for smithery.ai directory listing ## 0.1.6 - Fix MCP stdio compliance: accept notifications, advertise underscore tool names, and return CallToolResult `content` payloads so Codex/other MCP clients stay connected. - Keep docs/tests in sync with MCP spec responses ahead of npm publish. ## 0.1.5 - Ship MCP stdio mode (docdex.search/index/files/open/stats) with resource templates and docs for MCP-aware clients. - Expand CLI/help and tests around MCP usage to make agent/editor integration reliable. - Bump versions for the MCP release and upcoming npm publish. ## 0.1.4 - Bump version for republish after 0.1.3 was already on npm. - Keep trusted publishing fixes and expanded platform targets. ## 0.1.3 - Fix npm trusted publishing setup (environment + registry configuration) and bump version for release. - Add musl/Windows targets to the release workflow and doc updates for broader platform support. ## 0.1.2 - Add musl/Windows targets to the release workflow and align npm publish trigger on tags. - Doc updates for broader platform support. ## 0.1.1 - Bump version for npm doc updates and release alignment. ## 0.1.0 - Initial release of docdexd.

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bekirdag/docdex'

If you have feedback or need assistance with the MCP directory API, please join our Discord server