MCP Tools Directory
← Browse integrations

Developer tools

Thalovant MCP

Free account · sign-in required

Contact Thalovant MCP

Loading secure sign-in…

Tools for autonomous AI agents

Official website ↗

About this integration

Connect MCP clients to Thalovant control-plane and hub runtime APIs over stdio or Streamable HTTP.

Transport
stdio
Authentication
unknown
Initial setup
credentials
Runtime
unattended
Evidence
documented
Version
0.5.1
Package
@thalovant/mcp-server
Last compatibility test
Not independently tested

Connect your agent

@thalovant/mcp-server

Publisher documentation reviewed for the packaged stdio artifact and its credential-dependent Thalovant connection. Authentication is classified as unknown because the documented modes span scoped API tokens, access tokens, account login, and separate runtime identities. Write and destructive capabilities require carefully scoped credentials and operator policy; destructive tools are documented as disabled by default. The package and integration endpoints were not executed or independently security-audited.

Repository ↗Authentication & capability evidence ↗

Capabilities: Discover and administer Thalovant hubs and runtime groups, Inspect and manage hub skills, memory, and analytics, Send authenticated hub runtime queries, actions, code, and events

Connected profiles

Developer toolsindustries

Additional details

Registry identifier

io.github.thalovant/thalovant-mcp

Source ↗ · Checked 2026-09-17
Published version

0.5.1

Source ↗ · Checked 2026-09-17
Metadata license

CC0-1.0; package licenses are separate

Source ↗ · Checked 2026-09-17
Package ecosystem

npm

Source ↗ · Checked 2026-09-17
Source artifact

@thalovant/mcp-server

Source ↗ · Checked 2026-09-20
Source manifest version

0.5.2

Source ↗ · Checked 2026-09-20
Unattended configuration

The publisher documents a long-running stdio CLI with signal handling and bounded cleanup, suitable for launch and lifecycle management by an MCP client after configuration; this was documentation review only.

Source ↗ · Checked 2026-09-20
Authentication and prerequisites

Public hub discovery needs no Thalovant credential, while private control-plane functions select a scoped API token, pre-issued access token, or email/password login, and runtime tools use separate protected client identities. These multiple backend credential modes do not map to one native authentication class.

Source ↗ · Checked 2026-09-20
Connection configuration

The reviewed artifact communicates with local MCP clients over stdio without writing logs to stdout; its manifest exposes the thalovant-mcp executable. The existing listing remains stdio with no remote endpoint.

Source ↗ · Checked 2026-09-20
Review scope

Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.

Source ↗ · Checked 2026-09-20