plsql-test-mcp
This server automates IFS Cloud PL/SQL unit test generation and management for .plsql and .plsvc files, handling everything from testability analysis to test file creation and deployment preparation.
checkUnitTestability: Analyze a source file (or specific method) to determine if functions/procedures are unit testable, returning suggested@IgnoreUnitTestannotations for non-testable ones.annotateIgnoreUnitTest: Insert an@IgnoreUnitTest <reason>comment immediately before a specific method, with preview mode (confirmed=false) before writing changes.generateUnitTest: Generate or append apltstunit test block for a testable method, following IFS Developer Studio conventions including@MockTable/@MockPackageplaceholders, data-driven FOR loops, and assertions.processUnitTestCoverage: Batch process an entire source file — annotating all non-testable methods and generating all missing unit tests at once.runUnitTest: Prepare unit test execution by returninggenerate_and_deployinstructions for theifs-f1-codegen-devtool, targeting a specific database environment.runPlsqlTestWorkflow: End-to-end workflow that checks testability, annotates non-testable methods or generates tests as needed, and optionally prepares the test run — all in one step.getIgnoreUnitTestRules: Retrieve the full catalog of supported@IgnoreUnitTestannotation reasons (e.g.,DMLOperation,TrivialFunction,NoOutParams,PipelinedFunction, etc.).
Allows linking PL/SQL unit test generation and coverage to Jira issues via a jiraKey parameter.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@plsql-test-mcpCheck if Is_Circular_Link___ is unit testable"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PL/SQL Test MCP
MCP server for IFS Cloud PL/SQL unit testing — mirrors the architecture of integration-testing-mcp and delegates deploy/run steps to ifs-f1-codegen-dev.
Develop MCP to identify if a function/procedure is unit testable and generate the test.
Workflow
flowchart TD
A[checkUnitTestability] --> B{Testable?}
B -->|No| C[annotateIgnoreUnitTest]
B -->|Yes| D[generateUnitTest]
D --> E[generate_code / generate_and_deploy via ifs-f1-codegen-dev]
E --> F[Verify test passes]
C --> ERelated MCP server: mcp-playwright-test
Tools
Tool | Description |
| Parse |
| Add |
| Analyze method body, generate deploy-safe mocks, data-driven FOR loops, and assertions |
| Batch: annotate all non-testable methods + generate all missing auto-safe tests for one file |
| Return |
| End-to-end: check → annotate OR generate → run prep |
| List supported ignore reasons |
Supported @IgnoreUnitTest reasons
Reason | When to use |
| Simple getter/pass-through |
|
|
| INSERT/UPDATE/DELETE/MERGE in body |
| Procedure with no OUT/IN OUT params |
| EXECUTE IMMEDIATE / dynamic SQL |
| Large object types |
| PL/SQL embedded in SQL views |
| Pipelined table functions |
Cursor integration
Add to Cursor MCP settings:
{
"mcpServers": {
"plsql-test": {
"command": "node",
"args": ["C:/ifsapps-new/plsql-test-mcp/dist/index.js"]
}
}
}Or after publishing:
{
"mcpServers": {
"plsql-test": {
"command": "npx",
"args": ["-y", "@ifs/plsql-test-mcp@0.1.0"]
}
}
}Development
cd c:/ifsapps-new/plsql-test-mcp
npm install
npm run build
npm startDeploy-safe generation (v0.1.4)
The generator avoids patterns that break AV_*_TST compilation:
No UTF-8 BOM on written
.pltstfilesVARCHAR2(2000)for all generated IS-section locals (bareVARCHAR2causes PLS-00215)Pre-write validation rejects bare VARCHAR2, BOM, and post-loop generated tests
Skips
%ROWTYPEreturn types andSELECT * INTO %ROWTYPE(manual test required)Skips CRUD modify methods using
Get_Object_By_Id___+Unpack___Expression SELECT columns (
round(cast(...))) mapped to safe mock column namesFOR loop column order matches IFS convention:
expected_ | input_param_Not-found cases stay inside the FOR loop (no post-loop statements)
Skips
@IgnoreUnitTestwhen the method already has a UNITTEST blockSpecial mocks for
Get_Wp_Id,Has_Skills_Assigned_In_Turn,Get_Fault_Id_From_Record_Id,Get_AOS_Days,Get_Hm_Contract_Id_By_Barcode
Batch coverage example
processUnitTestCoverage({
sourceFile: "C:/ifsapps-new/workspace/adcom/source/adcom/database/AvFault.plsql",
workspace: "C:/ifsapps-new/workspace",
jiraKey: "PJZ-12345",
confirmed: true
})Example
Analyze McprActivityRelation.plsql:
checkUnitTestability({
sourceFile: "C:/ifsapps-new/workspace/prjrep/source/prjrep/database/McprActivityRelation.plsql",
methodName: "Is_Circular_Link___"
})Generate test:
generateUnitTest({
sourceFile: ".../McprActivityRelation.plsql",
methodName: "Is_Circular_Link___",
workspace: "C:/ifsapps-new/workspace",
jiraKey: "PJZ-12345",
confirmed: true
})Run via ifs-f1-codegen-dev:
generate_and_deploy({
input_files: [".../McprActivityRelation.plsql", ".../McprActivityRelation.pltst"],
environment_key: "26r1-dev-lkp",
workspace: "C:/ifsapps-new/workspace",
confirmed: true
})Note on plvst
IFS uses .pltst files for both .plsql and .plsvc unit tests. No separate .plvst extension exists in the codebase — this MCP targets .pltst.
Related
integration-testing-mcp — reference MCP architecture
ifs-f1-codegen-dev — code generation, SQLcl deploy, live DB inspect
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/VaruniAlwis/plsql-test-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server