kite-connect-mcp

Complete the Kite login by hand

complete_login

Finish a Kite Connect login by exchanging a request_token copied from the browser address bar, storing the access token for all clients. Use it when the redirect page cannot be reached.

Instructions

Finish a Kite login with a request_token the person copied from the browser's address bar after logging in (use it when the redirect page could not be reached). Exchanges the token with Kite and stores the access token for every client of this server. Request tokens are single use and last only a few minutes. If KITE_MCP_ALLOWED_USER_ID is set, a login by any other Kite account is ended and refused.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "request_token": "<request_token>"
    },
    "name": "complete_login"
  }
}

Input Schema

Name	Required	Description	Default
`state`	No	the state from the same URL (optional; if given it must be valid)
`request_token`	Yes	the request_token from the address bar after logging in at Kite; the whole redirected URL (which also carries the state) is accepted too

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 6, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare it is a non-read-only, non-idempotent, open-world call; the description adds substantive behavior the annotations cannot express. It discloses that the token is exchanged with Kite and the access token is stored for every client of this server (a shared, session-wide side effect), that request tokens are single use and expire in minutes, and that KITE_MCP_ALLOWED_USER_ID causes other accounts' logins to be ended and refused.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action and the condition that selects it, followed by side effects and then the security constraint. No filler and no restatement of the name or title.

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?

For a two-parameter auth-completion tool with no output schema, the description covers source of input, downstream side effect, token lifetime, and account restriction. It does not say what a successful call returns or how to confirm the new session (e.g. via session_status), which is the only material gap.

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 coverage is 100%, and the schema already explains both request_token (including that a full redirected URL is accepted) and state. The description reinforces where the token comes from but adds no syntax, format, or validation meaning beyond the schema, so the baseline of 3 applies.

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?

States a concrete verb and resource ('Finish a Kite login with a request_token') and immediately pins down the exact input source ('copied from the browser's address bar after logging in'). The parenthetical '(use it when the redirect page could not be reached)' separates it from the normal login sibling, so an agent can pick between them without opening either schema.

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?

Gives a clear triggering condition: use this when the redirect page could not be reached, i.e. the fallback path for login. It stops short of naming the primary login tool explicitly or stating 'do not use this for a normal login', so the alternative is implied rather than spelled out.

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