Schema | mcp-viva-engage

mcp-viva-engage

Describes the environment variables required to run the server.

Name	Required	Description	Default
`AZURE_CLIENT_ID`	Yes	Your Azure application (client) ID from App registration
`AZURE_TENANT_ID`	Yes	Your Azure directory (tenant) ID from App registration

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
get_networksA	Get all Viva Engage networks the user belongs to
get_communitiesA	Get all Viva Engage communities/groups the user is a member of in their home network
get_community_by_idA	Get details of a specific Viva Engage community by its ID
get_community_messagesB	Get all messages/posts in a specific Viva Engage community in the home network
get_threadC	Get all messages in a specific conversation thread
search_messagesA	Search for posts and messages across all communities in the home network
post_messageC	Post a new message to a Viva Engage community
reply_to_messageB	Reply to an existing message or conversation thread
get_storyline_feedA	Get the current user's Viva Engage storyline/personal feed

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pranav4186/mcp-viva-engage'

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