PropelAuth Integration MCP Server

PropelAuth Frontend Framework Integration

integrate_propelauth_frontend

Read-onlyIdempotent

Returns instructions for integrating PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered, optionally with API calls; use the integrate_propelauth_fullstack tool for fullstack integration that uses server-side rendering). Guidance includes installation and configuration, creating access tokens, retrieving user or org information, logging users out, redirecting users to login, and more. It is important to follow the instructions carefully to ensure a successful integration. Do not update the guidance argument unless the user explicitly requests it

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "integrate_propelauth_frontend"
  }
}

Input Schema

Name	Required	Description	Default
`guidance`	No
`frontend_framework`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedJun 5, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- removedOutput schema / description
```
Removed value: -"Generic wrapper for non-object return types."
```
Changed1 schema field changedApr 15, 2026
- addedOutput schema / description
```
Added value: +"Generic wrapper for non-object return types."
```
First observedApr 15, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is clear. The description adds that the tool 'returns instructions' and includes a caution to follow instructions carefully, plus a warning not to update the guidance argument unless explicitly requested. These are useful behavioral constraints beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is three sentences, all providing substantive information: purpose, examples, differentiation, content scope, and a usage caution. No fluff, though it could be slightly tightened. The last sentence about the guidance argument is an important agent instruction, adding value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has an output schema and readOnlyHint, the description does not need to explain return values. It covers the tool's purpose, alternative tool, content areas, and a usage constraint. The only gap is the parameter value mismatch (TypeScript/Next.js not in schema), which is a minor completeness issue.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It lists example guidance topics (installation, access tokens, user info, logout, login) and frontend frameworks (React, JavaScript, TypeScript), but the schema enums only include Javascript and React, creating confusion by mentioning TypeScript and Next.js. It also does not enumerate all guidance values, so it only partially explains the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns instructions for integrating PropelAuth in frontend frameworks, with specific examples (React, JavaScript, TypeScript, Next.js). It also distinguishes itself from the sibling tool integrate_propelauth_fullstack by explicitly naming it, making purpose and differentiation unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly directs users to use integrate_propelauth_fullstack for fullstack integration with server-side rendering, providing a clear when-not-to-use. It also defines the frontend context (client-side rendered, optionally with API calls). However, it does not contrast with backend or OAuth alternatives, so it is not a full usage guide.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PropelAuth Integration MCP Server tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?