Industry solutionsPublic source

Student Records MCP Server

A full Student Information System (SIS) for ADK-Rust Enterprise education agents. 46 MCP tools covering students, courses & enrollment, grades & rubric scoring, attendance, support cases, guardians & communications,…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Students — demographics, enrollment status, accommodations (IEP/504/ELL)

Courses & sections — catalog + term offerings with grade-category weights

Enrollment — student↔section with status

Grades & rubrics — assignment grades, rubric scoring (criterion sums), and a weighted gradebook → letter grade

Attendance — records + computed rate

Support — intervention cases with notes and status

Guardians & communications — guardian links with consent; messaging

Architecture

How Student Records MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

Student Records MCP Server

Validates the request and owns 27 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

Student Records MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Student Records MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

46 named tools

find_students

Find students by SIS id, name, or grade level (FERPA-logged)

read only

get_student

Get a student's record (FERPA read)

read only

set_student_status

Set a student's enrollment status

internal write

add_accommodation

Add an IEP/504/ELL accommodation to a student

internal write

get_access_log

Get the FERPA access log (accounting of disclosures) for a student

read only

create_course

Create a catalog course

internal write

list_courses

List catalog courses

read only

create_section

Create a course section with grade-category weights

internal write

enroll

Enroll a student in a section

internal write

get_enrollments

List a student's enrollments (FERPA read)

read only

create_assignment

Create an assignment in a section

internal write

record_grade

Record a grade (with optional rubric) for a student

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

23 read only22 internal write1 external write

The registry manifest declares read only, internal write, external write tool risk classes.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-student-records

ADK-Rust connection shape

let toolset = McpToolset::from_stdio(
    "mcp-student-records",
    ["mcp-student-records"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Architecture ↗docs/architecture.svg Issues and support ↗github.com issues

Keep exploring

Student Records MCP Server

A purpose-built capability behind one MCP connection.

How Student Records MCP Server fits into an agent system.

ADK-Rust agent

MCP client

Student Records MCP Server

Domain system

The server’s published architecture

What can an agent ask Student Records MCP Server to do?

Understand the effect of every tool.

What the current documentation declares.

Follow the project’s documented starting point.

Continue with the project maintainers’ source of truth.

More in industry solutions.