Add session info to auth_login tool response

[Copilot]

Summary

The auth_login tool now provides comprehensive session information in its success response, giving the model immediate context about the authenticated user and server configuration without requiring an additional get_me tool call.

Why

Eliminates wasteful get_me tool call after authentication. Provides the model with a "warm start" by including user details and configuration directly in the auth_login response text that the model receives.

What changed

• Added GetSessionInfo callback to AuthToolDependencies to generate session context after authentication
• Modified pollAndComplete function to fetch and include user info and configuration in auth_login success message
• Auth_login response now includes formatted session information with:
  • User account details (username, name, email, company, location, profile URL)
  • Enabled toolsets and tools
  • Configuration flags (read-only, lockdown, dynamic toolsets)
• Removed "Call get_me to see who you're logged in as" from auth_login success message (no longer needed)

MCP impact

• No tool or API changes
• Tool schema or behavior changed
• New tool added

The auth_login tool's response text now includes comprehensive session information. No schema changes, but the response content is significantly enhanced.

Prompts tested (tool changes only)

N/A - This change enhances the existing auth_login tool's response without altering its invocation or parameters.

Security / limits

• No security or limits impact
• Auth / permissions considered
• Data exposure, filtering, or token/size limits considered

User info is fetched using the authenticated token and only included in the auth_login response after successful authentication. Reuses existing get_me endpoint with same permissions.

Lint & tests

• Linted locally with ./script/lint
• Tested locally with ./script/test

Docs

• Not needed
• Updated (README / docs / examples)

The enhanced response is part of the auth_login tool output and doesn't require documentation changes.

Example

After successful authentication, the auth_login tool returns:

✅ Successfully authenticated with GitHub!

All GitHub tools are now available.

## Your GitHub Account

**Username:** @octocat
**Name:** The Octocat
**Email:** [email protected]
**Company:** GitHub
**Location:** San Francisco
**Profile:** https://github.com/octocat

## Server Configuration

**Enabled Toolsets:** context, repos, issues, pull_requests, users
**Configuration:**
- Read-only mode (if enabled)
- Lockdown mode (if enabled)
- Dynamic toolsets (if enabled)

This information is provided directly in the tool response text, which the model receives as part of the conversation, giving it immediate context without requiring a follow-up get_me call.

Original prompt

Would you look at returning the response of get me as part of the success response rather than suggesting making a tool call. If it fails just omit it, that feels more natural. We don't need to prove anything.

We could tell the user also the toolsets (or all or default) enabled, individual tools specifically enabled and if readonly mode or lockdown mode are on or not.

Is that a cool idea? Make it so the user gets a really great start to their authenticated session. Without wasting a second tool call.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[SamMorrowDrums]

@copilot this is not quite right, it's a good hook initialize, however the meta property is not received by the model, and the host application itself is the bit that knows the configuration so meta won't help it.

The idea here was that the model would get a warm start without additional tool calls, so that a newly authenticated session would be clear what the user has (given they don't have the tools to inspect as only auth tool is present), so we were looking at providing it in the main payload.

[Copilot]

@copilot this is not quite right, it's a good hook initialize, however the meta property is not received by the model, and the host application itself is the bit that knows the configuration so meta w...

You're absolutely right! I've updated the implementation to include session information in the auth_login tool's response text instead of _meta or instructions.

After successful authentication, the auth_login tool now returns comprehensive session context including:

• User account details (username, name, email, company, location, profile URL)
• Enabled toolsets and tools
• Configuration flags (read-only, lockdown, dynamic toolsets)

This provides the model with a "warm start" without requiring an additional tool call. The session info is formatted as readable text in the tool response that the model receives.

Changes in commit 6d30396.