Skip to content
WidyaaTalk to us

Developers / MCP

Connect your agent to Widyaa.

Give your agent a school identity connection that you approve and control. Start with account authentication, agent registration, and identity verification.

Open Widyaa MCP Read the setup guide

A connection you control

Your school account identifies you. Your consent authorizes the agent. You can revoke that access at any time.

Start with your school account

The MCP service currently connects to one configured Widyaa Schools deployment. Sign in with your existing school email and password, or accept an invitation issued by your school administrator. Public account signup is unavailable.

Your agent needs an OAuth client that supports authorization code with S256 PKCE and manual client registration. Compatibility with a specific hosted assistant depends on that client’s setup options.

Connect in five steps

  1. Open Widyaa MCP and sign in, or accept your school invitation.
  2. Open Agents and register your agent’s name and exact HTTPS callback URL. Copy the public client ID that is created for your application.
  3. Configure your agent with that client ID, the MCP endpoint https://mcp.widyaa.com/mcp, and the scope erp.identity. Use the same endpoint URL as the OAuth resource. The agent starts the authorization code flow with S256 PKCE.
  4. Review the account, agent, callback URL, and requested access on the consent page. Approve the request to let the agent exchange its one-use code for an access token.
  5. Ask the connected client to list its tools and call auth_status to verify the school identity and authorization status.

Registering an agent creates a public client ID. Access begins only after you approve its separate authorization request. A public client ID does not require a client secret.

What is available today

The current tool, auth_status, returns a minimal verified school identity and authorization status. School records such as attendance, fees, admissions, and academics are outside this early-access integration.

Access tokens last up to 10 minutes and cannot outlive your school sign-in. There are no refresh grants or automatic sign-in renewal. Sign in and approve access again after expiry.

From Agents, you can revoke an individual authorization, revoke a registered agent, or disconnect your current school sign-in. Disconnecting revokes the authorizations connected to that sign-in.

Discover the connection

Widyaa publishes a public AI catalog pointing to the MCP service’s server card. Clients can use these documents to find the transport endpoint before connecting. The API catalog also links the endpoint, server description, and this setup guide using standard web link relations.

Authentication metadata belongs to the MCP service:

Send MCP access tokens in the Authorization: Bearer header. Keep passwords, invitation tokens, and access tokens out of chat messages and tool arguments; enter school credentials only on the first-party sign-in page.

Building an integration?

Contact mohit@blupp.co with your client name and the workflow you want to connect. Real-school sign-in and client compatibility should be verified for your integration before relying on it.