MCP tool monetization

[shanakama]

Purpose

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Checklist

• Verified that llms.txt (located at en/docs/llms.txt) is updated for AI readiness content.
• Ensured meaningful alt text for images and that the information contained in an image also appears in text so the relevant info exists in the body of the document.
• Added or updated frontmatter for the respective pages.

Goals

Describe the solutions that this feature/fix will introduce to resolve the problems described above

Approach

Describe how you are implementing the solutions. Include an animated GIF or screenshot if the change affects the UI (email documentation@wso2.com to review all UI text). Include a link to a Markdown file or Google doc if the feature write-up is too long to paste here.

User stories

Summary of user stories addressed by this change>

Release note

Brief description of the new feature or bug fix as it will appear in the release notes

Documentation

Link(s) to product documentation that addresses the changes of this PR. If no doc impact, enter “N/A” plus brief explanation of why there’s no doc impact

Training

Link to the PR for changes to the training content in https://github.com/wso2/WSO2-Training, if applicable

Certification

Type “Sent” when you have provided new/updated certification questions, plus four answers for each question (correct answer highlighted in bold), based on this change. Certification questions/answers should be sent to certification@wso2.com and NOT pasted in this PR. If there is no impact on certification exams, type “N/A” and explain why.

Marketing

Link to drafts of marketing content that will describe and promote this feature, including product page changes, technical articles, blog posts, videos, etc., if applicable

Automation tests

• Unit tests

  Code coverage information

• Integration tests

  Details about the test cases and coverage

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines? yes/no
• Ran FindSecurityBugs plugin and verified report? yes/no
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets? yes/no

Samples

Provide high-level details about the samples related to this feature

Related PRs

List any other related PRs

Migrations (if applicable)

Describe migration steps and platforms on which migration has been tested

Test environment

List all JDK versions, operating systems, databases, and browser/versions on which this feature/fix was tested

Learning

Describe the research phase and any blog posts, patterns, libraries, or add-ons you used to solve the problem.

[coderabbitai]

📝 Walkthrough

Added a new monetization guide for MCP tools that explains how to set up and validate tool-call billing with the self-hosted gateway.

Also updated the documentation navigation to link to the new guide under Guides → Monetization.

Walkthrough

Adds a new documentation guide for monetizing MCP tool calls through the self-hosted gateway and adds it to the Monetization navigation. The guide covers prerequisites, gateway and MCP proxy setup, enabling Moesif analytics, restarting the gateway, generating authenticated traffic, creating a usage-based meter, connecting Stripe, verification checks, troubleshooting, and related next steps.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is just the template and lacks the required filled sections, issue links, goals, approach, and test details.	Fill in the template sections with the actual purpose, goals, approach, checklist status, related docs, tests, and any links or N/A notes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the main change: adding MCP tool monetization docs.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

en/docs/guides/monetization/mcp-tool-monetization.md (1)

196-196: 🔒 Security & Privacy | 🔵 Trivial | 💤 Low value

Consider adding a production note for als_plain_text.

The als_plain_text = true setting sends analytics events over unencrypted gRPC. For production deployments, configure TLS for the gRPC event server to prevent exposing analytics data in transit.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@en/docs/guides/monetization/mcp-tool-monetization.md` at line 196, Add a
production note for the als_plain_text configuration in the monetization guide:
this setting uses unencrypted gRPC for analytics events, so update the
documentation around als_plain_text to clearly warn that production deployments
should enable TLS on the gRPC event server to keep analytics data encrypted in
transit.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@en/docs/guides/monetization/mcp-tool-monetization.md`:
- Line 196: Add a production note for the als_plain_text configuration in the
monetization guide: this setting uses unencrypted gRPC for analytics events, so
update the documentation around als_plain_text to clearly warn that production
deployments should enable TLS on the gRPC event server to keep analytics data
encrypted in transit.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 84c8088f-85b0-4ab8-aa64-99348b3e9d86

📥 Commits

Reviewing files that changed from the base of the PR and between 6f16f54 and 7792ba6.

📒 Files selected for processing (2)

• en/docs/guides/monetization/mcp-tool-monetization.md
• en/mkdocs.yml