Skip to content
This repository was archived by the owner on Apr 12, 2026. It is now read-only.

Add user profile information to MCP tool calls#23

Open
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1747342394-add-user-profile-to-mcp
Open

Add user profile information to MCP tool calls#23
devin-ai-integration[bot] wants to merge 1 commit into
mainfrom
devin/1747342394-add-user-profile-to-mcp

Conversation

@devin-ai-integration
Copy link
Copy Markdown

@devin-ai-integration devin-ai-integration Bot commented May 15, 2025

Add user profile information to MCP tool calls

Addresses issue #19 by sending the Slack user's email address and profile information to MCP when executing tool calls.

Changes

  • Modified the data flow to pass the user ID through the pipeline
  • Added code to retrieve the user's profile information using the Slack API
  • Added the user profile information to the arguments passed to MCP tools

The user profile is added to the tool call arguments under the 'user_profile' key, which includes all profile fields such as email, real name, display name, etc.

Note: For this to work, the Slack application must have the appropriate OAuth scopes: users:read and users:read.email to access the user's email address.

Link to Devin run: https://app.devin.ai/sessions/884dbd1847ba41f79028e28e129386ef
Requested by: Tommy Nguyen ([email protected])

Summary by CodeRabbit

  • New Features
    • Integrated Slack user profile information into language model responses and tool executions, enabling more personalized interactions within Slack.
  • Bug Fixes
    • Improved logging for user profile retrieval and integration, enhancing transparency and traceability during Slack interactions.

@devin-ai-integration
Copy link
Copy Markdown
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 15, 2025

Walkthrough

The changes update several method signatures to include user profile or user ID parameters, enabling user-specific context to be incorporated into LLM response processing and tool invocation. User profile information is now fetched and passed through the processing pipeline, with appropriate logging and error handling added for profile retrieval.

Changes

File(s) Change Summary
internal/handlers/llm_mcp_bridge.go Updated ProcessLLMResponse and executeToolCall method signatures to accept a userProfile parameter. Passed this parameter through the call chain and added logic to include it in tool call arguments if present, with debug logging.
internal/slack/client.go Updated handleUserPrompt and processLLMResponseAndReply method signatures to include userID. Fetched user profile using userID and Slack API client, logged results, and passed profile to LLM processing. Adjusted all internal calls accordingly.

Sequence Diagram(s)

sequenceDiagram
    participant SlackUser
    participant SlackClient
    participant LLMBridge
    participant ToolCall

    SlackUser->>SlackClient: Sends user prompt (includes userID)
    SlackClient->>SlackClient: Fetch user profile using userID
    SlackClient->>LLMBridge: ProcessLLMResponse(..., userProfile)
    LLMBridge->>ToolCall: executeToolCall(..., userProfile)
    ToolCall->>ToolCall: Add user_profile to Args if present
    ToolCall-->>LLMBridge: Return result
    LLMBridge-->>SlackClient: Return processed response
    SlackClient-->>SlackUser: Reply with response
Loading

Poem

In the warren where user profiles dwell,
We pass them along, as the code will now tell.
From Slack to the bridge, with context in tow,
Each hop brings more knowledge, each log helps us grow.
🐰✨ User-aware bunnies, onward we go!

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Free
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 54af459 and df6822e.

📒 Files selected for processing (2)
  • internal/handlers/llm_mcp_bridge.go (3 hunks)
  • internal/slack/client.go (6 hunks)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@tuannvm
Copy link
Copy Markdown
Owner

tuannvm commented May 15, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 15, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@devin-ai-integration
Copy link
Copy Markdown
Author

Closing due to inactivity for more than 7 days.

@tuannvm tuannvm reopened this Jun 9, 2025
@tuannvm
Copy link
Copy Markdown
Owner

tuannvm commented Jun 9, 2025

@coderabbitai review

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 9, 2025

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant